0.9.1

[John A. Martin]

Is this pubring stuff a problem or just a kink?  Should gpg wait to
try to grab the pubring until it has something to do?

-------------- cut here ---->8 ---< head
$ echo Helo | gpg --clearsign

You need a passphrase to unlock the secret key for
user: "John A. Martin <jam at acm.org>"
1024-bit DSA key, ID BFE25F2F, created 1998-09-19

Enter passphrase:
gpg: Interrupt caught ... exiting
$
$ echo Helo | gpg --clearsign | gpg
gpg: /home/jam/.gnupg/pubring.gpg: can't open gdbm file: Can't be writer
gpg: keyblock resource `/home/jam/.gnupg/pubring.gpg': file open error
gpg: OOPS in close enum_keyblocks - ignored
gpg: key BFE25F2F: secret key without public key - skipped
gpg: OOPS in close enum_keyblocks - ignored
gpg: key 3B986635: secret key without public key - skipped

You need a passphrase to unlock the secret key for
user: "John A. Martin <jam at acm.org>"
1024-bit DSA key, ID BFE25F2F, created 1998-09-19

Enter passphrase:
gpg: Interrupt caught ... exiting

gpg: Interrupt caught ... exiting
$
$ grep -v '^#' ~/.gnupg/options

no-greeting
lock-once
keyring gnupg-gdbm:~/.gnupg/pubring.gpg
no-default-keyring

load-extension skipjack
load-extension tiger
load-extension twofish

escape-from-lines
---- 8<------- cut here ----------> tail

Same without lock-once.

How about letting something like 'gpg --version -v', list the
effective options?

	jam