asks to run --check-trustdb too often

Bug #13031 reported by Michael P. Soulier
4
Affects Status Importance Assigned to Milestone
gnupg (Ubuntu)
Invalid
Low
James Troup

Bug Description

Every time I run

gpg --check-trustdb

it returns something like this when it's done.

gpg: next trustdb check due at 2005-03-05

But the next day, it tells me to run it again, when it shouldn't need running
for weeks according to its own output.

Seems kinda broken to me.

Revision history for this message
Matt Zimmerman (mdz) wrote :

I've seen this as well; every time I turn around it is nagging me about
--check-trustdb.

Revision history for this message
Dennis Kaarsemaker (dennis) wrote :

You probably have auto-downloading of keys enabled. This way you will quite
often have new public keys in your keyring that are not in your trustdb. It's a
feature that gpg nags, not a bug. The no-auto-check-trustdb option might help.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

As Dennis points out (I happened past this code just now) it's nagging you because you've introduced new keys into your keyring which therefore means you need a trustdb

The nag is perfectly valid

Changed in gnupg:
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.