[EPEL-devel] EPEL conflicts with Satellite 6 packages
There are a number of packages in EPEL 6 and 7 that conflict with packages provided by either RH Satellite or the katello-agent. A quick run through for an up to date (6.1.9) install of satellite on RHEL 7: bouncycastle.noarch 1.50-1.el7 epel createrepo_c.x86_64 0.9.0-1.el7epel createrepo_c-libs.x86_64 0.9.0-1.el7epel fasterxml-oss-parent.noarch 24-2.el7 epel hiera.noarch 1:1.3.4-5.el7 epel jackson-core.noarch 2.6.3-1.el7epel libqpid-dispatch.x86_64 0.5-2.el7 epel mod_passenger.x86_64 4.0.53-4.el7 epel mongodb.x86_64 2.6.11-1.el7 epel mongodb-server.x86_642.6.11-1.el7 epel python-BeautifulSoup.noarch 1:3.2.1-7.el7 epel python-billiard.x86_64 1:3.3.0.20-2.el7 epel python-bson.x86_64 2.5.2-4.el7epel python-httplib2.noarch 0.7.7-3.el7epel python-mongoengine.noarch0.8.8-1.el7epel python-okaara.noarch 1.0.35-1.el7 epel python-pymongo.x86_642.5.2-4.el7epel python-pymongo-gridfs.x86_64 2.5.2-4.el7epel python-qpid.noarch 0.32-13.el7epel python-qpid-proton.x86_640.12.1-1.el7 epel python-qpid-qmf.x86_64 0.32-1.el7 epel python-simplejson.x86_64 3.3.3-1.el7epel qpid-cpp-client.x86_64 0.34-6.el7 epel qpid-cpp-client-devel.x86_64 0.34-6.el7 epel qpid-cpp-server.x86_64 0.34-6.el7 epel qpid-cpp-server-linearstore.x86_64 0.34-6.el7 epel qpid-dispatch-router.x86_64 0.5-2.el7 epel qpid-proton-c.x86_64 0.12.1-1.el7 epel qpid-qmf.x86_64 0.32-1.el7 epel qpid-tools.noarch0.32-9.el7 epel ruby-shadow.x86_64 1.4.1-23.el7 epel rubygem-ffi.x86_64 1.9.3-1.el7epel rubygem-rack.noarch 1:1.6.4-2.el7 epel rubygem-rack-protection.noarch 1.5.3-3.el7epel rubygem-rest-client.noarch 1.6.7-4.el7epel rubygem-rkerberos.x86_64 0.1.3-5.el7epel v8.x86_641:3.14.5.10-17.el7 epel Obsoleting Packages passenger.x86_64 4.0.53-4.el7 epel rubygem-passenger-native-libs.x86_64 4.0.18-21.el7sat @rhel-7-server-satellite-6.1-rpms passenger.x86_64 4.0.53-4.el7 epel rubygem-passenger-native.x86_64 4.0.18-21.el7sat @rhel-7-server-satellite-6.1-rpms passenger.x86_64 4.0.53-4.el7 epel rubygem-passenger.x86_64 4.0.18-21.el7sat @rhel-7-server-satellite-6.1-rpms These packages may/may not clobber satllite, which is a bit of a delicate flower. On the client side katello-agent for RHEL 6 (at least) uses the following packages: qpid-proton-c python-qpid-proton Possibly others on the client side, I am having a more difficult time pulling that list out right now. I was under the impression that for good or bad EPEL should not conflict with RHEL packages, I may be wrong about this, but I wanted to check. -Erinn ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org
[EPEL-devel] EPEL conflicts with Satellite 6 packages
There are a number of packages in EPEL 6 and 7 that conflict with packages provided by either RH Satellite or the katello-agent. A quick run through for an up to date (6.1.9) install of satellite on RHEL 7: bouncycastle.noarch 1.50-1.el7 epel createrepo_c.x86_64 0.9.0-1.el7epel createrepo_c-libs.x86_64 0.9.0-1.el7epel fasterxml-oss-parent.noarch 24-2.el7 epel hiera.noarch 1:1.3.4-5.el7 epel jackson-core.noarch 2.6.3-1.el7epel libqpid-dispatch.x86_64 0.5-2.el7 epel mod_passenger.x86_64 4.0.53-4.el7 epel mongodb.x86_64 2.6.11-1.el7 epel mongodb-server.x86_642.6.11-1.el7 epel python-BeautifulSoup.noarch 1:3.2.1-7.el7 epel python-billiard.x86_64 1:3.3.0.20-2.el7 epel python-bson.x86_64 2.5.2-4.el7epel python-httplib2.noarch 0.7.7-3.el7epel python-mongoengine.noarch0.8.8-1.el7epel python-okaara.noarch 1.0.35-1.el7 epel python-pymongo.x86_642.5.2-4.el7epel python-pymongo-gridfs.x86_64 2.5.2-4.el7epel python-qpid.noarch 0.32-13.el7epel python-qpid-proton.x86_640.12.1-1.el7 epel python-qpid-qmf.x86_64 0.32-1.el7 epel python-simplejson.x86_64 3.3.3-1.el7epel qpid-cpp-client.x86_64 0.34-6.el7 epel qpid-cpp-client-devel.x86_64 0.34-6.el7 epel qpid-cpp-server.x86_64 0.34-6.el7 epel qpid-cpp-server-linearstore.x86_64 0.34-6.el7 epel qpid-dispatch-router.x86_64 0.5-2.el7 epel qpid-proton-c.x86_64 0.12.1-1.el7 epel qpid-qmf.x86_64 0.32-1.el7 epel qpid-tools.noarch0.32-9.el7 epel ruby-shadow.x86_64 1.4.1-23.el7 epel rubygem-ffi.x86_64 1.9.3-1.el7epel rubygem-rack.noarch 1:1.6.4-2.el7 epel rubygem-rack-protection.noarch 1.5.3-3.el7epel rubygem-rest-client.noarch 1.6.7-4.el7epel rubygem-rkerberos.x86_64 0.1.3-5.el7epel v8.x86_641:3.14.5.10-17.el7 epel Obsoleting Packages passenger.x86_64 4.0.53-4.el7 epel rubygem-passenger-native-libs.x86_64 4.0.18-21.el7sat @rhel-7-server-satellite-6.1-rpms passenger.x86_64 4.0.53-4.el7 epel rubygem-passenger-native.x86_64 4.0.18-21.el7sat @rhel-7-server-satellite-6.1-rpms passenger.x86_64 4.0.53-4.el7 epel rubygem-passenger.x86_64 4.0.18-21.el7sat @rhel-7-server-satellite-6.1-rpms These packages may/may not clobber satllite, which is a bit of a delicate flower. On the client side katello-agent for RHEL 6 (at least) uses the following packages: qpid-proton-c python-qpid-proton Possibly others on the client side, I am having a more difficult time pulling that list out right now. I was under the impression that for good or bad EPEL should not conflict with RHEL packages, I may be wrong about this, but I wanted to check. -Erinn ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org
