OK for users to upgrade OM Lx 4.0 now (2019-05-05)

Today the most recent mass rebuild was completed but there will be some chain builds. Because of this users are advised to delay upgrading as things may be a bit messy until all this “catching up” from the recent ABF server crash is finished.

Our gpg key was recovered and the --nogpgcheck option is no longer needed by dnf.

There is more information here.

1 Like

Someone will announce here when all this is finished. At which time upgrades will likely go smoother.

1 Like

We do apologize for any inconvenience our user may have encountered with upgrading OM Lx 4 recently.

However it is extremely important for all users to remember we are still using cooker repos, expecting no issues is not a reasonable expectation. There will be a repo split soon and OM Lx 4 will have it’s own repos and thus isolated from the consequences of developer work that happens in Cooker. There should also be a new ISO at that time. We will announce both on the forum when it happens.

As of today it should be OK for users to upgrade their OM Lx 4 systems.

Not everyone will have the same or all of the errors mentioned, you only need to take the steps that address the errors that occur on your system. If you don’t see any errors, then don’t worry, be happy and upgrade as you normally do. That is if you normally use the command line to upgrade. Dnfdragora or Discover upgrades are still not recommended. (Seriously don’t do that.)

It is impossible to anticipate every possible problem on any Linux distro with upgrading however it is likely that a lot of users will see something like this:

$ sudo dnf clean all

$ sudo dnf --refresh upgrade
OpenMandriva Cooker - x86_64 - non-free                                                               126 kB/s | 161 kB     00:01    
OpenMandriva Cooker - x86_64 - Restricted                                                             114 kB/s | 141 kB     00:01    
OpenMandriva Cooker - x86_64                                                                          2.7 MB/s |  14 MB     00:05    
 Problem 1: cannot install the best update candidate for package gstreamer1.0-plugins-bad-1.14.4-2.x86_64
  - nothing provides libfluidsynth.so.1()(64bit) needed by gstreamer1.0-plugins-bad-1.14.4-2.x86_64
 Problem 2: cannot install both kwave-19.04.0-2.x86_64 and kwave-1:18.12.3-1.x86_64
  - package kwave-19.04.0-2.x86_64 obsoletes kwave < 1:19.04.01-2 provided by kwave-1:18.12.3-1.x86_64
  - cannot install the best update candidate for package lib64kwave18-1:18.12.3-1.x86_64
  - problem with installed package kwave-1:18.12.3-1.x86_64
 Problem 3: cannot install both libqalculate-data-3.1.0-1.noarch and libqalculate-data-2.9.0-1.noarch
  - package lib64qalculate20-2.9.0-1.x86_64 requires libqalculate-data = 2.9.0-1, but none of the providers can be installed
  - cannot install the best update candidate for package libqalculate-data-2.9.0-1.noarch
  - problem with installed package lib64qalculate20-2.9.0-1.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

To get past these:

Problem 1:

Download from Index of /cooker/repository/x86_64/main/release/ gstreamer1.0-plugins-bad.

Next we are going to remove and then install gstreamer1.0-plugins-bad like this:

$ sudo rpm -e --nodeps gstreamer1.0-plugins-bad

Next we cd to the directory where you downloaded gstreamer1.0-plugins-bad perhaps this:

$ cd /home/<uname>/Downloads

Now install the new gstreamer1.0-plugins-bad:

$ sudo rpm -ihv --nodeps gstreamer1.0-plugins-bad-1.16.0-1-omv4000.x86_64.rpm

That should take care of Problem 1 if you have it.

Problem 2 and Problem 3 if you have them:

Now just as a one time thing we will add an option (–allowerasing) to normal upgrade command. This will remove the offending packages in problems 2 & 3 and install their updated replacements:

$ sudo dnf --refresh --allowerasing upgrade

Then to be sure we got everything:

$ sudo dnf --refresh upgrade

And that should do the job. It is a good idea to periodically run ‘dnf autoremove’ to remove any packages that were installed as dependencies but are no longer used.

It is always a good practice to run ‘dnf clean all’ before doing any package management from command line. Among other things this cleans the cache to ensure that you are installing the most recent packages. Also helps to eliminate confusion some times. So do it.

:hear_no_evil: :speak_no_evil: :see_no_evil: