Bug 729521 - spacewalk-common packages requires newer version of selinux-policy-base than what's available
Summary: spacewalk-common packages requires newer version of selinux-policy-base than ...
Alias: None
Product: Spacewalk
Classification: Community
Component: Installation
Version: 1.5
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jan Pazdziora
QA Contact: Red Hat Satellite QA List
Depends On:
Blocks: space16
TreeView+ depends on / blocked
Reported: 2011-08-10 02:45 UTC by Paul Ehrenreich
Modified: 2011-08-10 09:24 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-08-10 06:51:23 UTC

Attachments (Terms of Use)

Description Paul Ehrenreich 2011-08-10 02:45:29 UTC
Description of problem:

installing the spacewalk-oracle package fails due to spacewalk-common-1.5.1-1 requiring selinux-policy-base >= 3.7.19-93. The latest version of selinux-policy-base available for CentOS 6 is selinux-policy-minimum-3.7.19-54.el6.noarch

Version-Release number of selected component (if applicable):

spacewalk 1.5.1
Centos 6.0 

How reproducible:

every time 

Steps to Reproduce:
1. yum install spacewalk-oracle

Actual resulError: Package: spacewalk-common-1.5.1-1.el6.noarch (spacewalk)                                                   
           Requires: selinux-policy-base >= 3.7.19-93                                                             
           Installed: selinux-policy-targeted-3.7.19-54.el6_0.5.noarch (@updates)                                 
               selinux-policy-base = 3.7.19-54.el6_0.5                                                            
           Available: selinux-policy-minimum-3.7.19-54.el6.noarch (base)                                          
               selinux-policy-base = 3.7.19-54.el6                                                                
           Available: selinux-policy-minimum-3.7.19-54.el6_0.3.noarch (updates)                                   
               selinux-policy-base = 3.7.19-54.el6_0.3                                                            
           Available: selinux-policy-minimum-3.7.19-54.el6_0.5.noarch (updates)                                   
               selinux-policy-base = 3.7.19-54.el6_0.5                                                            
           Available: selinux-policy-mls-3.7.19-54.el6.noarch (base)                                              
               selinux-policy-base = 3.7.19-54.el6                                                                
           Available: selinux-policy-mls-3.7.19-54.el6_0.3.noarch (updates)                                       
               selinux-policy-base = 3.7.19-54.el6_0.3                                                            
           Available: selinux-policy-mls-3.7.19-54.el6_0.5.noarch (updates)                                       
               selinux-policy-base = 3.7.19-54.el6_0.5                                                            
           Available: selinux-policy-targeted-3.7.19-54.el6.noarch (base)                                         
               selinux-policy-base = 3.7.19-54.el6                                                                
           Available: selinux-policy-targeted-3.7.19-54.el6_0.3.noarch (updates)                                  
               selinux-policy-base = 3.7.19-54.el6_0.3                                                            
 You could try using --skip-broken to work around the problem                                                     
 You could try running: rpm -Va --nofiles --nodigest            

Expected results:

installation completed successfully?

Additional info:

Comment 1 Jan Pazdziora 2011-08-10 06:51:23 UTC
The newer selinux-policy is essential for correct operation of Spacewalk on RHEL 6. Yes, it's part of RHEL 6.1 release. The fact that CentOS did not release that update is unfortunate but really nothing Spacewalk team would be dedicated on fixing.

You can build the selinux-policy from sources:


Comment 2 Paul Ehrenreich 2011-08-10 09:24:28 UTC
Thanks Jan, I'll give that a shot!

Note You need to log in before you can comment on or make changes to this bug.