Niibe, good catch. Hopefully addressed in 0e1729bb993648deca84a2664ae78edc848d7003.

I just commited 386a7bbb245dd3ab7c4156a554adbe75d82bdf49, that should fix your troubles with the test suite in the short term.

Interesting. What about gpg-agent? I don't see problems in the log you mentioned.

Can you elaborate that?

I translated index.de.org, donate.de.org, and checkout-cc.de.org. I don't see anything missing in procdonate.cgi.

I have not looked at this since I did some work on the pinentries, but if noone fixed this then yes, it is still an issue. Indeed, I just quickly read over the source:

Please change the template so that the boilerplate is considered a signature by separating it with '--\n' so that it can be folded away by MUAs.

The OpenPGP test suite is now run once with keyboxes and once with keyrings, so backend-specific bug like this will be caught in the future.

Automatic creation of socket directories creates cleanup trouble for projects previously relying on the agent-shutdown if $GNUPGHOME is removed: https://notmuchmail.org/pipermail/notmuch/2017/024550.html

In T3080#96945, @languitar wrote:

Any plans when this change will be pushed into a release version so that it ends up in distros?

This seems to work just fine on our archlinux box with the nsswitch configuration above.

In T2844#96255, @marcus wrote:

phabricator already mirrors these repositories, and the mirrors are accessible via https, e.g. https://dev.gnupg.org/source/gnupg.git
How about just pointing to these and leave git.gnupg.org git-only?

This bug affects GnuPG 2.1.20 when using keyrings (I guess most users upgrading from older versions do). This is fixed in 22739433e98be80e46fe7d01d52a9627c1aebaae.

I just used three 'GnuPG-bug-id: xxx' lines and only the last one is displayed: rG22739433e98be80e46fe7d01d52a9627c1aebaae