Bug 113261 - errors related to selinux
Summary: errors related to selinux
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: rpm
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Paul Nasrat
QA Contact: Mike McLean
URL:
Whiteboard:
: 113689 116652 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-01-11 14:41 UTC by Kaj J. Niemi
Modified: 2007-04-18 17:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-19 18:42:01 UTC
Embargoed:


Attachments (Terms of Use)

Description Kaj J. Niemi 2004-01-11 14:41:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b)
Gecko/20031218

Description of problem:
On a system where SELinux is _not_ enabled rpm 4.3-0.6 complains (at
least) while installing or verifying packages about a missing
SELinux-related file:

% rpm -V net-snmp
/etc/security/selinux/src/policy/file_contexts/file_contexts: No such
file or directory

It seems cosmetic in nature as package verification and installation
still works.

The path might also be wrong (2x file_contexts)

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

How reproducible:
Always

Steps to Reproduce:
1. rpm -V foo
2.
3.
    

Additional info:

Comment 1 Jeff Johnson 2004-01-11 14:51:01 UTC
Yup.

NEEDINFO until decisions are made (and so I don't have to
stare at this bug).

Comment 2 Jeff Johnson 2004-01-16 16:10:54 UTC
*** Bug 113689 has been marked as a duplicate of this bug. ***

Comment 3 Miloslav Trmac 2004-02-24 19:03:58 UTC
*** Bug 116652 has been marked as a duplicate of this bug. ***

Comment 4 Ben Levenson 2004-02-27 16:57:36 UTC
*** Bug 114456 has been marked as a duplicate of this bug. ***

Comment 5 Jeremy Katz 2005-04-19 18:42:01 UTC
Closing due to inactivity.  If this issue still occurs with current releases,
please reopen and set the release in which you've encountered the problem.


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