Bug 1265578

Summary:	rpm-plugin-systemd-inhibit would deserve some documentation
Product:	Red Hat Enterprise Linux 7	Reporter:	Karel Srot <ksrot>
Component:	rpm	Assignee:	Florian Festi <ffesti>
Status:	CLOSED ERRATA	QA Contact:	Karel Srot <ksrot>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.2	CC:	ffesti
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rpm-4.11.3-18.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-04 04:37:33 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:

Description Karel Srot 2015-09-23 09:23:10 UTC

Description of problem:

As we have backported the plugin to 7.2 (bug 1160401) it would be good to have it also documented, e.g. in a for of a manpage or at least README file.

Version-Release number of selected component (if applicable):
rpm-plugin-systemd-inhibit-4.11.3-17.el7

# rpm -ql rpm-plugin-systemd-inhibit.
/usr/lib64/rpm-plugins
/usr/lib64/rpm-plugins/systemd_inhibit.so

No doc.

Comment 3 Karel Srot 2016-07-08 07:18:37 UTC

Hi Florian,
I can see you have added the man page and it is part of the rpm package. Is there a reason for not shiping it with the rpm-plugin-systemd-inhibit subpackage itself? For example rpm-sign subpackage ships the man page on its own.

# rpm -ql rpm | grep plugin
/usr/share/man/man8/rpm-plugin-systemd-inhibit.8.gz
# rpm -ql rpm-plugin-systemd-inhibit
/usr/lib64/rpm-plugins
/usr/lib64/rpm-plugins/systemd_inhibit.so
# rpm -ql rpm-sign
/usr/bin/rpmsign
/usr/share/man/man8/rpmsign.8.gz

Comment 4 Karel Srot 2016-07-27 11:22:17 UTC

It doesn't make sense to do another respin just due to changing the file location. Therefore I have file new bug 1360706 regarding the man page location.

Comment 7 errata-xmlrpc 2016-11-04 04:37:33 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-2359.html