Bug 1296867

Summary:	SELinux man pages are placed in -devel subpackage instead of -doc subpackage.
Product:	Red Hat Enterprise Linux 7	Reporter:	Miroslav Grepl <mgrepl>
Component:	selinux-policy	Assignee:	Lukas Vrabec <lvrabec>
Status:	CLOSED ERRATA	QA Contact:	Milos Malik <mmalik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	lvrabec, mgrepl, mmalik, peljasz, plautrba, pvrabec, ssekidde
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	selinux-policy-3.13.1-80.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-04 02:40:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1292790

Description Miroslav Grepl 2016-01-08 09:53:04 UTC

Description of problem:

SELinux man pages for services are placed in selinux-policy-devel package instead of selinux-policy-targeted package.

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

rpm -qf /usr/share/man/man8/httpd_selinux.8.gz 
selinux-policy-devel-3.13.1-50.el7.noarch

Comment 2 Lukas Vrabec 2016-03-19 21:55:28 UTC

*** Bug 1266555 has been marked as a duplicate of this bug. ***

Comment 3 lejeczek 2016-03-21 16:04:10 UTC

I'll vote - as in bug report - to put them in default/main package, no doc. These are very important in my mind. Admins will be looking straight for selinux man pages even on minimal installations, and doc part does not come by default.

Comment 4 Mike McCune 2016-03-28 22:59:28 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 7 Lukas Vrabec 2016-06-16 12:08:25 UTC

Milos, could you test it with the latest build? I would say it's fixed.

Comment 13 errata-xmlrpc 2016-11-04 02:40:08 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2283.html