Re: gnupg migration corrupt db?

On Fri, 2015-05-15 at 20:28 +0100, MFPA wrote: > > > How do I check if they are PGP2 keys? > > If they are, they will have a shorter fingerprint which is commonly > presented as 16 separate double hex digits. > ; Then no, they are not PGP2

Re: gnupg migration corrupt db?

On Fri, 2015-05-15 at 13:37 +0200, Werner Koch wrote: > > > gpg: keydb_get_keyblock failed: Value not found > > gpg: key 77731557: public key "[User ID not found]" imported > > gpg: key 77731557: failed to re-lookup public key > > Please update to 2.1.4 2.1.2 has some problems skipping PGP-2 key

Re: gnupg migration corrupt db?

On Fri, 2015-05-15 at 13:37 +0200, Werner Koch wrote: > > gpg: keydb_get_keyblock failed: Value not found > > gpg: key 77731557: public key "[User ID not found]" imported > > gpg: key 77731557: failed to re-lookup public key > > Please update to 2.1.4 2.1.2 has some problems skipping PGP-2 keys.

Re: gnupg migration corrupt db?

On Fri, 2015-05-15 at 13:37 +0200, Werner Koch wrote: > On Thu, 14 May 2015 13:16, berend.de.schou...@gmail.com said: > > > Right now gnupg1 works, but gnupg2 does not. With that, I mean > > gnupg1 > > can decrypt, but gnupg2 cannot decrypt the same files. The reason > > seems to be a failure t

gnupg migration corrupt db?

Hi, On my system both gnupg 1.4.19 and 2.1.2 are installed. I'm still trying to track down what needs what. gnupg2 seems to have attempted to automatically migrate my DB from an older version to a newer version on first execution. However, it seems to have failed: gpg: starting migration from