Bug 120239

Summary: installing policy-sources creates both policy.15 and policy.16
Product: [Fedora] Fedora Reporter: Alexandre Oliva <oliva>
Component: policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED NOTABUG QA Contact: Ben Levenson <benl>
Severity: low Docs Contact:
Priority: medium    
Version: rawhideCC: pgraner
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-04-07 10:58:29 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 Alexandre Oliva 2004-04-07 02:39:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312

Description of problem:
The post-install script of policy-sources creates both
/etc/security/selinux/policy.`cat /selinux/policyvers` and
/etc/security/selinux/policy.15 (from PREVPOLICYVER).

Version-Release number of selected component (if applicable):
policy-sources-1.9.2-12

How reproducible:
Always

Steps to Reproduce:
1.rm -f /etc/security/selinux/*
2.up2date -u policy-sources (upgrading from the previous version)

Actual Results:  It works, but an old policy file is created and left
behind.

Expected Results:  I don't see why it should be created, but it should
definitely not be left behind.

Ideally, if the newly-generated policy is identical to the file
installed by the policy rpm, it shouldn't be replaced, such that
.rpm{save,new} files aren't created on the next update.

Additional info:

Comment 1 Daniel Walsh 2004-04-07 10:58:29 UTC
We are installing both because you might have a kernel on the machine
that only supports 15.  So if you boot that kernel you need 15.  We
will have this problem when we go to 17, 18...

We might be able to drop 15 when we go to the test3