Bug 122146 - running yum triggers selinux warnings
Summary: running yum triggers selinux warnings
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: rawhide
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords: SELinux
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-30 21:37 UTC by Florin Andrei
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2004-07-10 13:08:05 UTC


Attachments (Terms of Use)

Description Florin Andrei 2004-04-30 21:37:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116

Description of problem:
I'm just doing "yum install blah" type-of-thing. It pretty much works
fine, however, it vomits a bunch of selinux warnings, even though
selinux is supposedly disabled in FC2t3.
There are hundreds of warnings, i'm only copy/pasting a few:

/etc/security/selinux/file_contexts:  invalid context
root:object_r:staff_home_xauth_t on line number 1853
/etc/security/selinux/file_contexts:  invalid context
system_u:object_r:default_context_t on line number 1854
/etc/security/selinux/file_contexts:  invalid context
system_u:object_r:amanda_recover_dir_t on line number 1855
/etc/security/selinux/file_contexts:  invalid context
system_u:object_r:staff_home_spamassassin_t on line number 1856

Is it an issue with selinux? With yum?
I'm not even sure it's a bug proper - feel free to close the ticket if
i'm talking through my hat.

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


How reproducible:
Always

Steps to Reproduce:
1.run "yum install ..."
2.
3.
    

Actual Results:  hundreds upon hundreds of selinux warnings

Expected Results:  no warnings, 'cause selinux is allegedly turned off

Additional info:

For a description of the system (hardware, how i installed it), have a
look at bug #122043

Comment 1 Leonard den Ottolander 2004-05-11 09:14:59 UTC
Are you still seeing these errors?

Comment 2 Jeff Johnson 2004-07-10 13:08:05 UTC
Closed for lack of input.


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