Upgrading to OM Lx 4.1 pre-Beta (2019-12-27)

Tags: #<Tag:0x00007fe466235350> #<Tag:0x00007fe466234f68> #<Tag:0x00007fe466234bd0>

Post-edit: This applies to upgrading any previously installed OM Lx 4.1 Alpha or Rolling systems. They are currently using the same repositories.

Today in preparation for releasing OM Lx 4.1 Beta @bero did a “cp cooker rolling”. This will give users about 900 or more package to upgrade, re-install, and one downgrade for java13 if you have that installed. To do this you want to:

sudo dnf clean all

sudo dnf distro-sync

but first you will see this error:

# dnf distro-sync
Last metadata expiration check: 0:10:51 ago on Tue 24 Dec 2019 02:38:51 PM CST.
Error: 
 Problem: package lib64orcus0.14_0-0.14.1-3.x86_64 requires libboost_filesystem.so.1.71.0()(64bit), but none of the providers can be installed
  - lib64boost_filesystem1.71.0-1.71.0-2.x86_64 does not belong to a distupgrade repository
  - problem with installed package lib64orcus0.14_0-0.14.1-3.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

To get past that error this will work:

For x86_64 system:
sudo rpm -e --nodeps lib64orcus0.14_0-0.14.1-3.x86_64 lib64orcus-parser0.14_0-0.14.1-3.x86_64

For znver1 system:
sudo rpm -e --nodeps lib64orcus0.14_0-0.14.1-3.znver1 lib64orcus-parser0.14_0-0.14.1-3.znver1

then do the:

sudo dnf clean all

sudo dnf distro-sync

dnf will install the replacement packages for the 2 you removed with ‘rpm -e --nodeps’. The replacements are:

For x86_64 system:

lib64orcus-parser0.15_0-0.15.3-1.x86_64
lib64orcus0.15_0-0.15.3-1.x86_64

For znver1 system:

lib64orcus-parser0.15_0-0.15.3-1.znver1
lib64orcus0.15_0-0.15.3-1.znver1

Sharp minded user might notice this bug with dnf.

1 Like

For me after this dnf distro-sync if I run ‘dnf autoremove’ it will remove these:

Removing:
 lib64poppler91                                 znver1                                 0.81.0-1                                        @rolling-znver1                                 3.4 M
 lib64procps7                                   znver1                                 3.3.15-4                                        @rolling-znver1                                  67 k
 lib64rpm8                                      znver1                                 2:4.14.2.1-10                                   @rolling-znver1                                 577 k
 lib64rpmbuild8                                 znver1                                 2:4.14.2.1-10                                   @rolling-znver1                                 154 k
 lib64rpmsign8                                  znver1                                 2:4.14.2.1-10                                   @rolling-znver1                                  19 k

I have noticed no ill affects from removing those and the should no longer be needed. However there may be some package that complains of dependency for one of those. If you see such please report it and we’ll rebuild whatever packages have an issue.

Post-edit Note: As alway use ‘dnf autoremove’ with care and understanding if you are at all unsure about some packages it wants to remove then don’t do it. Ask here. If you do go ahead and run it write down what was removed if you need to re-install something. Or you can refer to ‘/var/log/dnf.log’ where all dnf transactions are logged.

1 Like

There is a x86_64 OM Lx 4.1 pre-Beta ISO here. My understanding is that packages will change little or none from this ISO for the actual Beta release. There may or may not be some difference in ISO features, I’m not clear on that at this time.

Newer and shinier OM Lx 4.1 x86_64 pre-Beta ISO here. With latest updates to Calamares installer and more.

Closing this thread. We’re about to do another “cp cooker rolling” and then we’ll build new ISO’s for OM Lx 4.1 Beta release.

The reason for doing “cp cooker rolling” is there may have been a thing or two missed in the python3.7>python3.8 upgrade. This particular upgrade is extremely complicated, involves a ton of packages, and certain things have to be done in a certain order or it is borked. So we are doing this in an abundance of caution to get this as correct as we possibly can.

1 Like