We had similar Dependency Resolution problems if katello-server has epel-release and our custom epel-repo installed at the same time on the system. So after removing epel-releae, we got our problem solved.
Am Dienstag, 6. Dezember 2016 04:29:52 UTC+1 schrieb Lachlan Musicman: > > Hi, > > We spent 3 months wrestling with Spacewalk before giving it up and moving > to Katello/Foreman early this year. > > Centos 7.2 is our main OS. Everything is up to date (or at least as up to > date as possible). Currently we have Foreman 1.12.4 w Katello 3.1.0, > "self-registered". > > I think I would like to update to Katello 3.2. The Katello update docs > implore us to make sure our system is up to date. > > One issue we have consistently had since we installed the system (on the > Katello server only) is a package conflict - every yum update gives us this > or something like it: > > 1063 packages excluded due to repository priority protections > Resolving Dependencies > --> Running transaction check > ---> Package python-qpid-proton.x86_64 0:0.13.1-1.el7 will be updated > ---> Package python-qpid-proton.x86_64 0:0.14.0-1.el7 will be an update > ---> Package python-qpid-qmf.x86_64 0:0.32-1.el7 will be updated > ---> Package python-qpid-qmf.x86_64 0:1.35.0-1.el7 will be an update > ---> Package qpid-cpp-client.x86_64 0:0.34-8.el7 will be updated > ---> Package qpid-cpp-client.x86_64 0:1.35.0-1.el7 will be an update > ---> Package qpid-cpp-client-devel.x86_64 0:0.34-8.el7 will be updated > ---> Package qpid-cpp-client-devel.x86_64 0:1.35.0-1.el7 will be an update > ---> Package qpid-cpp-server.x86_64 0:0.34-8.el7 will be updated > ---> Package qpid-cpp-server.x86_64 0:1.35.0-1.el7 will be an update > ---> Package qpid-cpp-server-linearstore.x86_64 0:0.34-8.el7 will be > updated > ---> Package qpid-cpp-server-linearstore.x86_64 0:1.35.0-1.el7 will be an > update > ---> Package qpid-proton-c.x86_64 0:0.13.1-1.el7 will be updated > --> Processing Dependency: libqpid-proton.so.7()(64bit) for package: > qpid-dispatch-router-0.6.0-2.katello.el7.x86_64 > ---> Package qpid-proton-c.x86_64 0:0.14.0-1.el7 will be an update > ---> Package qpid-qmf.x86_64 0:0.32-1.el7 will be updated > ---> Package qpid-qmf.x86_64 0:1.35.0-1.el7 will be an update > ---> Package qpid-tools.noarch 0:0.32-9.el7 will be updated > ---> Package qpid-tools.noarch 0:1.35.0-1.el7 will be an update > --> Finished Dependency Resolution > Error: Package: qpid-dispatch-router-0.6.0-2.katello.el7.x86_64 > (@Peter_MacCallum_Cancer_Centre_Katello_client) > Requires: libqpid-proton.so.7()(64bit) > Removing: qpid-proton-c-0.13.1-1.el7.x86_64 > (@Peter_MacCallum_Cancer_Centre_Extra_Packages_for_Enterprise_Linux_7_-_x86_64_epel) > libqpid-proton.so.7()(64bit) > Updated By: qpid-proton-c-0.14.0-1.el7.x86_64 > (Peter_MacCallum_Cancer_Centre_Extra_Packages_for_Enterprise_Linux_7_-_x86_64_epel) > ~libqpid-proton.so.8()(64bit) > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest > > > I have found this suggestion from many versions ago > > http://projects.theforeman.org/issues/10665 > > But that hasn't worked for us (with EPEL on a lower priority) > > 1. What have we done wrong? > 2. Is there a way to stop this conflict/error or resolve this issue? > 3. Can I just upgrade over the top of this issue? > 4. Does the upgrade make this go away? > > Cheers > L. > > ------ > The most dangerous phrase in the language is, "We've always done it this > way." > > - Grace Hopper > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
