Your message dated Mon, 28 Jul 2008 17:25:36 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#400822: gnupg: --no-options causes errors
has caused the Debian Bug report #400822,
regarding gnupg: --no-options causes errors
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
400822: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400822
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: gnupg
Version: 1.4.5-2
Severity: normal
If I understand correctly, "gpg --no-options" is supposed to ignore
~/.gnupg completely. However I get the following errors when using it:
$ echo foo | gpg -c --no-options >/dev/null
gpg: keyblock resource `/home/m/.gnupg/pubring.gpg': file open error
gpg: can't create `/home/m/.gnupg/random_seed': No such file or directory
$ echo $?
2
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (900, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages gnupg depends on:
ii gpgv 1.4.5-2 GNU privacy guard - signature veri
ii libbz2-1.0 1.0.3-6 high-quality block-sorting file co
ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries
ii libldap2 2.1.30-13+b1 OpenLDAP libraries
ii libreadline5 5.2-1 GNU readline and history libraries
ii libusb-0.1-4 2:0.1.12-2 userspace USB programming library
ii makedev 2.3.1-83 creates device files in /dev
ii zlib1g 1:1.2.3-13 compression library - runtime
gnupg recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
> > No, --no-options just ignores the gpg.conf file. Other things in
> > ~/.gnupg (keyrings, random_seed), are still used. Also, if you don't
> > have a ~/.gnupg, --no-options prevents automatically creating one
> > (which may be what happened in the example above).
>
> Yes, that's what happened and now when I think about it the behavior is as
> documented.
Ok, I'm closing this bug then.
Thijs
pgpJGG7bv5LAo.pgp
Description: PGP signature
--- End Message ---
