Bug 839126

Summary: rpm(8) manual page missing information about --setperms and --setugid
Product: Red Hat Enterprise Linux 6 Reporter: Murray McAllister <mmcallis>
Component: rpmAssignee: Panu Matilainen <pmatilai>
Status: CLOSED ERRATA QA Contact: Patrik Kis <pkis>
Severity: low Docs Contact:
Priority: low    
Version: 6.3CC: ffesti, kseifried, pkis, vdanen
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-21 10:51:36 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 Murray McAllister 2012-07-11 04:03:18 UTC
Description of problem:
The rpm(8) manual page mentions:

rpm {--setperms|--setugids} PACKAGE_NAME ...

--setperms sounds very useful, but there is no description of what it does or why you would use it in the manual page. Can that information please be added?

Version-Release number of selected component (if applicable):
rpm-4.8.0-27.el6.x86_64

Comment 1 Kurt Seifried 2012-07-11 04:07:43 UTC
Also --setugids is missing any information.

Comment 3 Florian Festi 2012-07-31 14:42:30 UTC
It probably worth checking the whole man page for missing parameters and then decide whether to add them all or to point to some external documentation.

Comment 4 RHEL Program Management 2012-08-14 21:59:48 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release.  Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.

Comment 10 errata-xmlrpc 2013-02-21 10:51:36 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.

http://rhn.redhat.com/errata/RHBA-2013-0461.html