Bug 140831

Summary: selinux-policy-targeted update creates *.rpmnew files
Product: [Fedora] Fedora Reporter: Bernd Bartmann <bernd.bartmann>
Component: selinux-policy-targetedAssignee: Daniel Walsh <dwalsh>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-11 21:51:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Bernd Bartmann 2004-11-25 10:17:44 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0

Description of problem:
The selinux-policy-targeted update 1.17.30-2.34 leaves .rpmnew files
lying around. This make the update useless as Joe user has no idea how
to handle .rpmnew files.

Here is the list of the *.rpmnew files I found after the update:


Also were is the announcement for the update?

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

How reproducible:

Steps to Reproduce:
1. update to latest selinux-policy-targeted

Additional info:

Comment 1 Daniel Walsh 2004-11-30 16:55:17 UTC
These files are being created because you installed
selinux-policy-targeted-sources and that install updated the policy.18
and file_contexts file.

We are working on newer versions and ways of fixing this problem.  You
can replace the policy.18 and file context file with the rpmnew file.


Comment 2 Bernd Bartmann 2004-11-30 19:27:19 UTC
Ok, do I have to re-run some tool like after the renaming or a reboot?
How does the new policy come into effect?

Comment 3 Daniel Walsh 2004-11-30 19:29:07 UTC
You can do a mv 

mv policy.18.rpmnew policy.18
load_policy policy.18

And you are done.