Possible problem upgrading ROME (2023-07-05)

[ben79 (Ben Bullard)]

As announced here there was just a major software upgrade for OM ROME branch.

If user sees any error similar to this, or any error message that mentions 5.240.0 packages:

* Problema 1: package plasma-desktop-5.27.5-1.x86_64 from @System requires libkworkspace5.so.5()(64bit), but none of the providers can be installed
* - cannot install both lib64kworkspace5-5.240.0-0.20230527.1.x86_64 from rolling-x86_64 and lib64kworkspace5-5.27.5-1.x86_64 from @System
* - cannot install both lib64kworkspace5-5.27.5-1.x86_64 from rolling-x86_64 and lib64kworkspace5-5.240.0-0.20230527.1.x86_64 from rolling-x86_64
* - cannot install the best update candidate for package plasma-desktop-5.27.5-1.x86_64
* - cannot install the best update candidate for package lib64kworkspace5-5.27.5-1.x86_64

You do not want to install those packages. Those packages are for the future when Plasma 6 is released and the Plasma 6 packages are packaged for OMLx by OM developers. To workaround these errors run this command in Konsole (terminal):

$ sudo dnf clean all ; sudo dnf dsync -x *5.240.0*

Some users may see these issues:

Printing from Chromium crashes browser (The workaround is to use Falkon or other browser if you need to print something from browser)

Can’t login from sddm with new user passwd. (Workaround: sudo dnf rm kwallet-pam)

nVidia proprietary drivers are not built yet for the new kernel-6.3.4-3. For now if user needs the proprietary driver then they need to use the old kernel. (Developers are working on this)

Note: I started this post about 2 weeks ago, apologies for not getting it posted sooner.

Note-2: Sometimes there are errors blocking a dsync that can be alleviated by using the --allowerasing option. OMLx user should be aware of this and use it if needed. Some people use this for all dsync transactions. You use it like this:

$ sudo --allowerasing dnf dsync

or

$ sudo --allowereasing dnf dsync -x *5.240.0*

Users that want to know more about dnf commands and options may read here. It is a good idea to know why we recommend commands like dnf clean all, or options like --refresh, and --alloweraing. There are other useful commands and options as well.

[ben79 (Ben Bullard)]

Documentation for the dnf clean command:

Clean Command
Command: clean

Performs cleanup of temporary files kept for repositories. This includes any such data left behind from disabled or removed repositories as well as for different distribution release versions.

dnf clean dbcache
Removes cache files generated from the repository metadata. This forces DNF to regenerate the cache files the next time it is run.

dnf clean expire-cache
Marks the repository metadata expired. DNF will re-validate the cache for each repository the next time it is used.

dnf clean metadata
Removes repository metadata. Those are the files which DNF uses to determine the remote availability of packages. Using this option will make DNF download all the metadata the next time it is run.

dnf clean packages
Removes any cached packages from the system.

dnf clean all
Does all of the above.

Documentation for the options mentioned in the previous post:

–allowerasing
Allow erasing of installed packages to resolve dependencies. This option could be used as an alternative to the dnf swap command where packages to remove are not explicitly defined.

–refresh
Set metadata as expired before running the command.

Using dnf clean all or dnf --refresh <command> ensures that the metadata is set as expired and the repositories are refreshed with the latest metadata. Old, out of date, metadata leads to errors in dnf transactions. As shown above dnf clean all also removes old files and rpm’s from cache.

So keep it clean folks!