* Ralf Hildebrandt ([EMAIL PROTECTED]) wrote: > Package: gnupg2 > Version: 2.0.8-1 > Severity: normal > > > $ gpg2 --update-trustdb > gpg: public key 5A92B1B1 is 26108 seconds newer than the signature > gpg: public key 5A92B1B1 is 26246 seconds newer than the signature > gpg: public key 5A92B1B1 is 26222 seconds newer than the signature > gpg: public key 90F89A7D is 4723 seconds newer than the signature > gpg: public key 90F89A7D is 4717 seconds newer than the signature > gpg: public key 90F89A7D is 4706 seconds newer than the signature > gpg: public key 90F89A7D is 4711 seconds newer than the signature > gpg: public key 90F89A7D is 4701 seconds newer than the signature > an mpi of size 0 is not allowed > gpg: keyring_get_keyblock: read error: Invalid packet > gpg: keyring_get_keyblock failed: Invalid keyring > gpg: failed to rebuild keyring cache: Invalid keyring > gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model > an mpi of size 0 is not allowed > gpg: keyring_get_keyblock: read error: Invalid packet > gpg: keydb_get_keyblock failed: Invalid keyring > gpg: validate_key_list failed > > This keyring works perfectly well with gpg. What's up here?
Is this fixed in 2.0.9? I think it may have been. -- Eric Dorland <[EMAIL PROTECTED]> ICQ: #61138586, Jabber: [EMAIL PROTECTED]
signature.asc
Description: Digital signature
