I have Katello 4.2.2 running nicely on Rocky8 (one of the more popular OS’s to repllace the old Centos8…)
Lately when I try yum updates, I get the following, which appears to be caused by conflict(s) between katello/foreman repos and EPEL8.
(If I disable epel8, I get a clean check and “Nothing to do”, but then I am not able to update rubygem-qpid-proton which comes from the katello repo?)
What is the uh, proper resolution here? Do I just skip using epel8? Or…?
[root@katello ~]# yum update
Last metadata expiration check: 1:08:03 ago on Fri 04 Feb 2022 12:04:10 PM CST.
Error:
Problem 1: package rubygem-qpid_proton-0.36.0-1.el8.x86_64 requires libruby.so.2.5()(64bit), but none of the providers can be installed
- cannot install the best update candidate for package rubygem-qpid_proton-0.32.0-3.el8.x86_64
- package ruby-libs-2.5.9-107.module+el8.4.0+592+03ff458a.x86_64 is filtered out by modular filtering
Problem 2: package python3-pulpcore-3.14.9-1.el8.noarch conflicts with python3-django-filter >= 2.5 provided by python3-django-filter-21.1-1.el8.noarch- cannot install the best update candidate for package python3-pulpcore-3.14.9-1.el8.noarch
- cannot install the best update candidate for package python3-django-filter-2.4.0-1.el8.noarch
Problem 3: package foreman-3.0.1-1.el8.noarch requires rubygem(net-ssh) = 4.2.0, but none of the providers can be installed- cannot install both rubygem-net-ssh-5.1.0-2.el8.noarch and rubygem-net-ssh-4.2.0-3.el8.noarch
- cannot install both rubygem-net-ssh-4.2.0-3.el8.noarch and rubygem-net-ssh-5.1.0-2.el8.noarch
- cannot install the best update candidate for package rubygem-net-ssh-4.2.0-3.el8.noarch
- cannot install the best update candidate for package foreman-3.0.1-1.el8.noarch
(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)