* simon raven <simon.ra...@gmail.com> [090302 06:46]:
> It would list 3 keys, one dead one that expired, my gmail one, and my
> k.o one. apt and such were probably seeing the expired one and trying to
> parse that, perhaps.
I've tried to make the manpage more explicit. Do you think the following
change is sufficient or do you have some idea how to further improve it?
< When this field is present, a Release.gpg file will be gener-
< ated. If the value is "yes" or "default", the default key is
< used. Otherwise the value will be given to libgpgme to deter-
< mine to key to use. (That should be roughly the one gpg
< --list-secret-keys value would output).
---
> When this field is present, a Release.gpg file will be gener-
> ated. If the value is "yes" or "default", the default key of
> gpg is used. Otherwise the value will be given to libgpgme to
> determine to key to use.
>
> If there are problems with signing, you can try
> gpg --list-secret-keys value
> to see how gpg could interprete the value. If that command does
> not list any keys or multiple ones, try to find some other value
> (like the keyid), that gpg can more easily associate with a
> unique key.
Thanks in advance,
Bernhard R. Link
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
