Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 76224 - Man page error: options --nopgp and --nogpg not supported
Man page error: options --nopgp and --nogpg not supported
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Depends On:
  Show dependency treegraph
Reported: 2002-10-18 08:38 EDT by Reiner Buehl
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-12-02 07:48:13 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 Reiner Buehl 2002-10-18 08:38:15 EDT
Description of problem:
The man page describes the command line options --nopgp and --nogpg for rpm --
checksig. If used, rpm fails with "--nopgp: unknown option"

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

How reproducible:

Steps to Reproduce:
rpm --checksig --nopgp <Package File>
rpm --checksig --noggp <Package File>

Actual Results:  --nopgp: unknown option
--noggp: unknown option

Expected Results:  Man page should not list the options or the option should 

Additional info:

Same issue was already reported as Bug #65494 in Rawhide but the bug report was 
closed without fixing either documentation or executable.
Comment 1 Jeff Johnson 2002-10-21 08:45:51 EDT
The documentation will be fixed in rpm-4.2.

Meanwhile, the options --nogpg and --nopgp
have been replace by --nosignature.

Comment 2 Giuseppe Raimondi 2002-12-02 07:48:06 EST
I don't know if this is the right place to point this out, but the documentation
in the errata for 8.0 in our webpages should be amended. they still contain the
--nogpg option to test the rpms.
Comment 3 Jeff Johnson 2002-12-02 10:04:49 EST
Probably, but this ain't the place to get that fixed.

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