Bug#400822: gnupg: --no-options causes errors

2006-11-30 Thread Werner Koch
On Thu, 30 Nov 2006 03:07, [EMAIL PROTECTED] said: Yes, that's what happened and now when I think about it the behavior is as documented. But what's the reasoning for not creating ~/.gnupg if it's still needed? It is not always needed. Salam-Shalom, Werner -- To UNSUBSCRIBE, email

Bug#400822: gnupg: --no-options causes errors

2006-11-29 Thread Markus Järvinen
David Shaw [EMAIL PROTECTED]: On Wed, Nov 29, 2006 at 12:24:48AM +0200, Markus Järvinen wrote: 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:

Bug#400822: gnupg: --no-options causes errors

2006-11-28 Thread Markus Järvinen
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

Bug#400822: gnupg: --no-options causes errors

2006-11-28 Thread David Shaw
On Wed, Nov 29, 2006 at 12:24:48AM +0200, Markus Järvinen wrote: 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