AL 9.x system. Runs great, but this morning I ran into an issue I don’t normally encounter on my Alma machines - ‘dependency hell’.
Looked at the available updates - saw 10-12 were available. Here are sokme of them (just for reference…) – all in the ‘baseos’ repo.
libblkid.i686 2.37.4-21.el9_7 baseos
libblkid.x86_64 2.37.4-21.el9_7 baseos
libbrotli.i686 1.0.9-9.el9_7 baseos
libbrotli.x86_64 1.0.9-9.el9_7 baseos
libfdisk.x86_64 2.37.4-21.el9_7 baseos
libmount.i686 2.37.4-21.el9_7 baseos
libmount.x86_64 2.37.4-21.el9_7 baseos
libsmartcols.x86_64 2.37.4-21.el9_7 baseos
But, when I try to update them, get all sorts of errors like the following (truncation of full list - basically, the following is repeated for each package):
Problem: package libblkid-devel-2.37.4-21.el9.x86_64 from @System requires libblkid = 2.37.4-21.el9, but none of the providers can be installed
- cannot install both libblkid-2.37.4-21.el9_7.i686 from baseos and libblkid-2.37.4-21.el9.i686 from @System
- cannot install both libblkid-2.37.4-21.el9_7.i686 from baseos and libblkid-2.37.4-21.el9.i686 from baseos
- cannot install both libblkid-2.37.4-21.el9_7.x86_64 from baseos and libblkid-2.37.4-21.el9.x86_64 from @System
- cannot install both libblkid-2.37.4-21.el9_7.x86_64 from baseos and libblkid-2.37.4-21.el9.x86_64 from baseos
- cannot install the best update candidate for package libblkid-devel-2.37.4-21.el9.x86_64
- cannot install the best update candidate for package libblkid-2.37.4-21.el9.i686
- cannot install the best update candidate for package libblkid-2.37.4-21.el9.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)
Tried the usual steps of clean out and remaking the dnf cache, but no luck.
So, in general, for an AL machine (and presumably some of my newer machines running AL 10.1), what is the preferred approach to resolving this sort of thing? I’m puzzled that the ‘struggle’ is between two repos I would have thought would be synced from the get-go: baseos and @system?
Thanks in advance.