Bug 1026317 - man page yum-security doesn't mention option --sec-severity
Summary: man page yum-security doesn't mention option --sec-severity
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum-utils
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Packaging Maintenance Team
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-04 12:06 UTC by Petr Spacek
Modified: 2014-10-14 04:38 UTC (History)
3 users (show)

Fixed In Version: yum-utils-1.1.30-27.el6
Doc Type: Bug Fix
Doc Text:
NO DOCS NEEDED
Clone Of:
Environment:
Last Closed: 2014-10-14 04:38:30 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1411 0 normal SHIPPED_LIVE yum-utils bug fix update 2014-10-14 00:54:50 UTC

Description Petr Spacek 2013-11-04 12:06:39 UTC 
Description of problem:
Option --sec-severity is missing in manual page yum-security.

Version-Release number of selected component (if applicable):
yum-plugin-security-1.1.30-14.el6.noarch
Comment 2 Petr Spacek 2013-11-04 12:31:17 UTC 
Note: This option is mentioned in RH413 course.
Comment 3 Zdeněk Pavlas 2013-11-04 12:34:37 UTC 
When the plugin is enabled and you run "yum --help", the output should include:

--sec-severity       Include security relevant packages, of this severity

We can add this to yum-security.8 if necessary.
Comment 4 Petr Spacek 2013-11-04 16:33:12 UTC 
"yum --help" prints that, but it is not mentioned in man page. Note that all other options are there.

I think that for consistency it would be great if we can make man pages consistent.
Comment 6 Valentina Mukhamedzhanova 2014-05-15 07:45:50 UTC 
Switching to the correct component.
Comment 12 errata-xmlrpc 2014-10-14 04:38:30 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-2014-1411.html
Note You need to log in before you can comment on or make changes to this bug.