On Sun 2019-06-23 15:00:40 -0700, James Moe via Gnupg-users wrote: > On 23/06/2019 11.53 AM, James Moe via Gnupg-users wrote: > >> gnupg does appear in the update log >> > Sigh. Typo. > gnupg does NOT appear in the update log. Nor does libscrypt.
Without having access to your pubring.gpg, it's hard to say what is
triggering this loop.
I also note that gpg version 2.2.5 is fairly old -- is it possible to
try to upgrade to a newer version?
> The repetitive part of the log starts at line 475.
The repetitions at 475 actually end at 8144, and different things appear
to be happening in that debug log up until you sent it an interrupt to
cancel.
Is it possible that your pubring.gpg is corrupt?
Can you replicate this with a minimal GNUPGHOME?
Can you try migrating from pubring.gpg to pubring.kbx and see if you
still have the same problem? A script for doing that migration is here
if you want to try:
https://salsa.debian.org/debian/gnupg2/blob/debian/master/debian/migrate-pubring-from-classic-gpg
(you might want to back up your ~/.gnupg/ before trying)
All the best,
--dkg
signature.asc
Description: PGP signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
