Bug 360521

Summary: selinux RPMs Generate Output
Product: [Fedora] Fedora Reporter: Daniel Qarras <dqarras>
Component: selinux-policy-targetedAssignee: Daniel Walsh <dwalsh>
Status: CLOSED RAWHIDE QA Contact: Ben Levenson <benl>
Severity: low Docs Contact:
Priority: low    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-12-29 14:23:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Daniel Qarras 2007-10-31 16:31:51 UTC 
Description of problem:
While installing/updating SELinux related RPMs on a system where SELinux is
disabled many of them produce output. E.g.,

  Updating  : selinux-policy-targeted      ####################### [24/64] 
libsepol.mls_from_string: invalid MLS context s0:s0
libsepol.mls_from_string: could not construct mls context structure
libsepol.context_from_record: could not create context structure
libsepol.context_from_string: could not create context structure
libsepol.sepol_context_to_sid: could not convert
system_u:object_r:fixed_disk_device_t:s0:s0 to sid
invalid context system_u:object_r:fixed_disk_device_t:s0:s0
libsemanage.semanage_install_active: setfiles returned error code 1.
semodule:  Failed!


Version-Release number of selected component (if applicable):
3.0.8-42.fc8

How reproducible:
Always

Steps to Reproduce:
1. Boot with SELinux disabled
2. Install/update SELinux related RPMs
3. Notice output
  
Actual results:
Output printed.

Expected results:
No output.

Additional info:
I believe any output from RPM installation/update is prohibited by RPM packaging
guidelines so I am reporting this issue.
Comment 1 Daniel Walsh 2007-11-01 16:03:17 UTC 
fixed in selinux-policy-3.0.8-44.fc7
Comment 2 Daniel Qarras 2007-12-29 14:23:01 UTC 
I can confirm that this is now fixed. Closing.