Hide Forgot
Description of problem: On RHEL-6.2, while using the latest CloudEngine puddle (or candidate) repository, attempting to install aeolus-all results in dependency failures. # yum install aeolus-all <snip> Error: Package: puppet-2.6.11-1.el6_1.noarch (ce-rhel-6-candidate) Requires: ruby(selinux) <snip> libselinux-ruby is a subpackage of libselinux. While libselinux is available via RHN in the RHEL base channel, libselinux-ruby is in the optional channel. Due to our customer support for the optional channel, CloudForms CloudEngine cannot rely on content from rhel-6-optional for production use. This bug is intended to track requesting libselinux-ruby be added to the RHN base channel. Version-Release number of selected component (if applicable): * puppet-2.6.11-1.el6_1.noarch * libselinux-ruby-2.0.94-5.2.el6.x86_64 How reproducible: * easy ... 100% reproducible Steps to Reproduce: 1. Install RHEL-6.2 and register to RHN 2. Yum update your system 3. Add a repository for the latest CloudEngine content -- http://download.lab.bos.redhat.com/rel-eng/repos/ce-rhel-6-candidate/x86_64 4. yum install aeolus-all Actual results: Error: Package: puppet-2.6.11-1.el6_1.noarch (ce-rhel-6-candidate) Requires: ruby(selinux) Expected results: No package conflicts Additional info:
VERIFIED changes from comment #10: # pwd /mnt/redhat/nightly/RHEL6.3-20120409.n.0/6 # find -name "libselinux-ruby*" ./Workstation/i386/os/Packages/libselinux-ruby-2.0.94-5.3.el6.i686.rpm ./Workstation/x86_64/os/Packages/libselinux-ruby-2.0.94-5.3.el6.x86_64.rpm ./Client/i386/os/Packages/libselinux-ruby-2.0.94-5.3.el6.i686.rpm ./Client/x86_64/os/Packages/libselinux-ruby-2.0.94-5.3.el6.x86_64.rpm ./ComputeNode/x86_64/os/Packages/libselinux-ruby-2.0.94-5.3.el6.x86_64.rpm ./Server/ppc64/os/Packages/libselinux-ruby-2.0.94-5.3.el6.ppc64.rpm ./Server/s390x/os/Packages/libselinux-ruby-2.0.94-5.3.el6.s390x.rpm ./Server/i386/os/Packages/libselinux-ruby-2.0.94-5.3.el6.i686.rpm ./Server/x86_64/os/Packages/libselinux-ruby-2.0.94-5.3.el6.x86_64.rpm # find -name "python-libguestfs*" ./Workstation/x86_64/os/Packages/python-libguestfs-1.16.15-1.el6.x86_64.rpm ./Client/x86_64/os/Packages/python-libguestfs-1.16.15-1.el6.x86_64.rpm ./ComputeNode/x86_64/os/Packages/python-libguestfs-1.16.15-1.el6.x86_64.rpm ./Server/x86_64/os/Packages/python-libguestfs-1.16.15-1.el6.x86_64.rpm # find -name "ruby-devel*" ./Workstation/i386/os/Packages/ruby-devel-1.8.7.352-7.el6_2.i686.rpm ./Workstation/x86_64/os/Packages/ruby-devel-1.8.7.352-7.el6_2.i686.rpm ./Workstation/x86_64/os/Packages/ruby-devel-1.8.7.352-7.el6_2.x86_64.rpm ./Client/i386/os/Packages/ruby-devel-1.8.7.352-7.el6_2.i686.rpm ./Client/x86_64/os/Packages/ruby-devel-1.8.7.352-7.el6_2.i686.rpm ./Client/x86_64/os/Packages/ruby-devel-1.8.7.352-7.el6_2.x86_64.rpm ./ComputeNode/x86_64/os/Packages/ruby-devel-1.8.7.352-7.el6_2.i686.rpm ./ComputeNode/x86_64/os/Packages/ruby-devel-1.8.7.352-7.el6_2.x86_64.rpm ./Server/ppc64/os/Packages/ruby-devel-1.8.7.352-7.el6_2.ppc.rpm ./Server/ppc64/os/Packages/ruby-devel-1.8.7.352-7.el6_2.ppc64.rpm ./Server/s390x/os/Packages/ruby-devel-1.8.7.352-7.el6_2.s390.rpm ./Server/s390x/os/Packages/ruby-devel-1.8.7.352-7.el6_2.s390x.rpm ./Server/i386/os/Packages/ruby-devel-1.8.7.352-7.el6_2.i686.rpm ./Server/x86_64/os/Packages/ruby-devel-1.8.7.352-7.el6_2.i686.rpm ./Server/x86_64/os/Packages/ruby-devel-1.8.7.352-7.el6_2.x86_64.rpm # find -name "ruby-rdoc*" ./Workstation/i386/os/Packages/ruby-rdoc-1.8.7.352-7.el6_2.i686.rpm ./Workstation/x86_64/os/Packages/ruby-rdoc-1.8.7.352-7.el6_2.x86_64.rpm ./Client/i386/os/Packages/ruby-rdoc-1.8.7.352-7.el6_2.i686.rpm ./Client/x86_64/os/Packages/ruby-rdoc-1.8.7.352-7.el6_2.x86_64.rpm ./ComputeNode/x86_64/os/Packages/ruby-rdoc-1.8.7.352-7.el6_2.x86_64.rpm ./Server/ppc64/os/Packages/ruby-rdoc-1.8.7.352-7.el6_2.ppc64.rpm ./Server/s390x/os/Packages/ruby-rdoc-1.8.7.352-7.el6_2.s390x.rpm ./Server/i386/os/Packages/ruby-rdoc-1.8.7.352-7.el6_2.i686.rpm ./Server/x86_64/os/Packages/ruby-rdoc-1.8.7.352-7.el6_2.x86_64.rpm
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0971.html