On Friday 06 Nov 2015 15:38:58 Andrew Savchenko wrote: > Hi, > > On Mon, 19 Oct 2015 10:57:37 +0200 Jean-Christophe Bach wrote: > > I have a very similar problem, at least concerning your 2nd point > > (duplicated keys). All my problems came when I updated gnupg from 1.x to > > 2.x. I tried to solve them by playing with different 2.x versions but > > with the last one it is broken: > > > > 1. I detect duplicated keys in the ring > > 2. some friends told me my signature was bad > > 3. I am not able to verify all the signatures with Mutt or Thunderbird > > (I do not understand why it works for some signatures and not for others) > > 4. with Thunderbird, I am not able anymore to sign/verify/cypher/decypher > > > > I think that it is related to your problems, but I have no clue to fix > > that. I would also appreciate any help. > > I got help on gnupg-users mail list on this issue, see > https://lists.gnupg.org/pipermail/gnupg-users/2015-October/054569.html > > Basically you need to re-import all your public keys, *delete* old > pubring.gpg file (new file format is pubring.kbx) and restart your > gpg-agent: > > gpg --export-ownertrust >myownertrust.lst > gpg --export >allmykeys.gpg > rm pubring.kbx > killall gpg-agent > gpg --import <allmykeys.gpg > > First command is a backup in case something will go wrong. > > Best regards, > Andrew Savchenko
Thank you for letting us know about this. I have not yet updated to 2.1.* so don't know if my systems are affected. Is there an e-news item or an ebuild message to notify the user? Perhaps you need to raise a bug, unless this problem occurs only on some setups. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
