Bug 1062328 - Selinux policy is installing /usr/lib/rpm/macros.d/macros.selinux-policy which causes rpm to be required to be installed.
Summary: Selinux policy is installing /usr/lib/rpm/macros.d/macros.selinux-policy whic...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-06 16:41 UTC by Daniel Walsh
Modified: 2014-11-19 14:41 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-19 14:41:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Daniel Walsh 2014-02-06 16:41:42 UTC
In some of the docker talks/minimum OS/Images world. We are looking to have limited packages installed and we noticed that selinux-policy was requiring rpm to be installed.

The reason for this is it packages  /usr/lib/rpm/macros.d/macros.selinux-policy  
And since /var/lib/rpm/macros.d is owned by rpm package, it gets sucked in.

I am looking for a way for this to not be required.  I could remove the file from the payload and just create the file in the post install.  

Or do you have any other ideas?

Comment 1 Panu Matilainen 2014-02-07 05:44:26 UTC
That seems like a text-book example of
https://fedoraproject.org/wiki/Packaging:Guidelines#The_directory_is_owned_by_a_package_which_is_not_required_for_your_package_to_function

Just have selinux-policy co-own the directory, no harm done as long as the permissions and ownership match (root, root, 0755).

Comment 2 Daniel Walsh 2014-02-14 19:53:34 UTC
Miroslav I just added these two directories to the spec file, could you build a rawhide version and we can check if the requires of rpm has disappeared.

Comment 3 Miroslav Grepl 2014-02-18 13:26:30 UTC
A new rawhide build is coming today.


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