Your message dated Fri, 07 Apr 2006 14:15:31 +0200
with message-id <[EMAIL PROTECTED]>
and subject line gnupg: --no-auto-check-trustdb went away?
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: gnupg
Version: 1.2.5-3
Severity: minor

Hello,

the manpage (but not --help) knows the option:

‐‐no‐auto‐check‐trustdb

but when I try this option it isn't recognized:

$ gpg -‐no‐auto‐check‐trustdb --sign-key 6d8abe71
gpg: Invalid option "-‐no‐auto‐check‐trustdb"


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (ignored: LC_ALL set to 
de_DE.UTF-8)

Versions of packages gnupg depends on:
ii  devfsd                      1.3.25-19    Daemon for the device file system
ii  libbz2-1.0                  1.0.2-1      A high-quality block-sorting file 
ii  libc6                       2.3.2.ds1-16 GNU C Library: Shared libraries an
ii  libldap2                    2.1.30-3     OpenLDAP libraries
ii  makedev                     2.3.1-75     Creates device files in /dev
ii  zlib1g                      1:1.2.1.2-1  compression library - runtime

-- no debconf information


--- End Message ---
--- Begin Message ---
> > $ gpg -‐no‐auto‐check‐trustdb --sign-key 6d8abe71
> > gpg: Invalid option "-‐no‐auto‐check‐trustdb"
> 
> The current version of gnupg seems to handle this option just fine; I
> think the bug can be closed?

A closer look at your copy-paste reveals that you called the option not
with regular dashes (-) but with some other lookalike dashes (‐) from
the UTF-8 charset which explains why it didn't work in your case.

Since it actually works and it seems to be a mistake, I'm closing the
bug.


Thijs

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to