Red Hat Bugzilla – Bug 145039
Unchanged selinux install needing .rpmnew files, anyway
Last modified: 2007-11-30 17:10:58 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
During a routine 'yum update' I noticed it creating .rpmnew files.
These (as I understand it) are created when changes to configuration
files have been changed, and a new configuration has been made
available. This is all well and good- no problem here.
The curiousity is that I've had selinux turned _off_ since the
install; it's not something I feel has matured just yet and I don't
need it, so I let it go. I can't wait to use it- it's brilliant...but
not just now, and not when I don't need it.
My concern here is that the rpms are refusing to overlay (unchanged)
files unnecessarily. It's not causing _me_ a problem, but it might
solve something in the future and help out somewhere.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Update, weeks ago
2. Update, today (getting a new selinux-targeted-policy)
3. Note the warming from rpm: Warning (filename) created as
Actual Results: The RPM warning is the concern; without changes, this
Expected Results: No warnings; just installing the config files over
This is a known problem, that was caused by a conflict of
selinux-policy-targeted and selinux-policy-targeted-sources.
If you move the file_contexts.rpmnew over file_contexts and
policy.18.rpmnew over policy.18 the problem should go away.
Ah; ok- I just wanted to make sure the relevant people were aware of
the problem. Thanks!
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.