Bug#619558: Does not need a GPG trustdb (/etc/apt/trustdb.gpg), just the trusted keyring
On Sun, Mar 27, 2011 at 03:13, Josh Triplett <josh@joshtriplett.org> wrote:
> On Sat, Mar 26, 2011 at 10:33:17AM +0100, David Kalnischkies wrote:
>> I think this is very similar to --secrect-keyring which isn't really needed,
>> but gpg seems to insist on having it around…
>
> --trustdb-name /dev/null seems to work just fine, as does
> --secret-keyring /dev/null.
It works as long as the keyring isn't changed, but if a key is added or
remove you will get the lovely message:
gpg: fatal: /dev/null: invalid trustdb
secmem usage: 1408/1408 bytes in 2/2 blocks of pool 1408/32768
The action is executed non the less, but gpg exits with non-zero status
and i don't think ignoring gpg failures is a good idea…
Best regards
David Kalnischkies
Reply to: