I just upgraded to gnupg 2.1.1 from ports and it breaks. :-(
Upon every operation I get the following error message:
gpg: keydb_search failed: invalid packet
A downgrade to gnupg-2.1.0_1 fixed this for now. I tried this on two 10.1 boxes using gnupg from ports and got the same result.
If I delete my keydb, it works. But that doesn't seem such a great idea. ;)
Auto-assigned to maintainer kuriyama@FreeBSD.org
It seems that some of my keys are the problem.
I just exported my private keys using gpg 2.1.0, created a fresh keyring with gpg 2.1.1 and re-imported the private keys. That works so far. Maybe the keyring is just too old (I use gpg since 1998 ;-)).
I'll try to move the important keys that way.
Same problem here.
On re-import of my keyring, I noticed that there are about 40 PGP-2 keys that haven't been imported. Maybe that's why the seamless migration does not work properly.
What I understand is, why does gnupg-2.1 ask for passphrases for each secret key? Import of secret keys always worked without such things.
The following recipe is based on information found here:
Please exercise caution!
$ gpg --export-ownertrust > otrust.txt
$ mv ~/.gnupg ~/.gnupg.old
$ mkdir ~/.gnupg
$ chmod 700 ~/.gnupg
$ gpg --import ~/.gnupg.old/pubring.gpg
$ gpg --import-ownertrust otrust.txt
$ gpg --import ~/.gnupg.old/secring.gpg
(In reply to Andriy Gapon from comment #4)
I've used a very similar method, after looking for hints on the web. Fact is no one expects a breakage caused by a minor update. Such a breakage should be announced with a big warning.
It would be even better when a new port "gnupg21" had been created in this case or at least, a pkg-message would appear with hints how to convert the keyring.
What I want to say is that I didn't like this change, because I have valuable things encrypted and it gave me a small shock. My first reaction was to look for backups, because I thought my keyring was broken.
Now everything is fine again, thanks.
I'm not opposed to adding a pkg-message about this. Do any of you feel like producing some pkg-message text for this?
I have the same kind of problem . Finally some of my friends tried to help me and fixed it. Hope this will be one of the post many of the people will get the answer for their doubts. For the best ERP in Dubai you can choose http://adeptsol.com/
Jens, do you still see this error, especially after today's 2.1.21 update?
(In reply to Adam Weinberger from comment #8)
Since I re-created my keyring as mentioned I haven't had any problems.
Thanks, Jens. I'm going to close out this PR, and when gnupg 2.2 comes around I'll aim to include a more helpful message about the upgrade.
MARKED AS SPAM