Bug 236029 - checkmodule manpage is incorrect
checkmodule manpage is incorrect
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: checkpolicy (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Josef Kubin
Ben Levenson
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2007-04-11 11:56 EDT by Linda Knippers
Modified: 2013-04-12 15:06 EDT (History)
1 user (show)

See Also:
Fixed In Version: RHBA-2007-1072
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-12-05 08:59:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Linda Knippers 2007-04-11 11:56:00 EDT
Description of problem:
The manpage for checkmodule describes a -d (debug) option that is
not actually implemented.  

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

How reproducible:

Steps to Reproduce:
Actual results:
checkmodule -d gives a usage message

Expected results:
Should either work or not be in the manpage.  

Additional info:
The -d option on checkpolicy does work.  It looks like checkmodule
was intended to do the same at some point (getopt arguments include
a -d option) but was never implemented or was removed.
Comment 1 RHEL Product and Program Management 2007-06-05 16:32:04 EDT
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release.  Since this
bugzilla is in a component that is not approved for the current
release, it has been closed with resolution deferred.  You may
reopen this bugzilla for consideration in the next release.
Comment 4 Daniel Walsh 2007-07-10 14:53:15 EDT
Fixed in checkpolicy-1.33.1-3
Comment 6 Josef Kubin 2007-11-15 17:02:17 EST
Fixed in checkpolicy-1.33.1-4
Comment 10 errata-xmlrpc 2007-12-05 08:59:17 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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