Revert to gnupg-2.5.22 because gnupg-2.5.23+ breaks mail/notmuch
mail/notmuch uses gmime -> gpgme -> gnupg to decrypt PGP-encrypted
messages, and check for that feature in it configure script. Since
commit 2e6549f5de5307e3e84c1ffa5e762d14266546ba
gpg: Preliminary support for importing some rfc-9980 secret keys.
gpg-agent now appears unable to export the "session key" used by notmuch
tests, so gpg has no key to pass back to gpgme/gmime. The code in
notmuch/configure mimics the code in notmuch/util/crypto.c so we can
expect this to be an actual regression. Revert to the previous gnupg
release to unbreak bulk builds and avoid regressions.
Reported by sthen@
update to got 0.129
- fix missing status code of staged files in log message template during commit
- remove empty dangling directories within refs/ when removing references
- do not add unversioned files to version control if a file addition is merged
- handle removal of UID_MAX and GID_MAX
- fix a problem where 'got revert' errors out in work trees with a path-prefix
- plug a memory leak caused by duplicate ignore patterns