[PATCH] doc: Fix --debug-level for all versions.

Werner Koch wk at gnupg.org
Thu Sep 25 09:04:20 CEST 2014


On Thu, 25 Sep 2014 01:13, isis at patternsinthevoid.net said:

> While fixing an issue in python-gnupg, [0] it was discovered that GnuPG
> (for 1.4.x, 2.0.x, and 2.1.x branches) actually expects to receive the
> `--debug-level` argument in the form of `--debug-level=guru`, not
> `--debug-level guru` (as the current manuals would lead one to believe).

Actually this seems to be a bug in 1.4 only:

  $ ~/b/gnupg-1.4/g10/gpg --debug-level advanced --version
  gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
  gpg: It is only intended for test purposes and should NOT be
  gpg: used in a production environment or with production keys!
  usage: gpg [options] [filename]
  
  $ ~/b/gnupg-2.0/g10/gpg2 --debug-level advanced --version
  gpg (GnuPG) 2.0.23-beta13
  [...]
  
I'll take a look at it.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.




More information about the Gnupg-devel mailing list