Was the fix part of a stable release? The beta was 4.2.1b55. Stable download on https://gpg4win.de/ is 4.3.1. Am I correctly assuming, that 4.3.1 includes the fix and this issue here can be closed?

2.2.44 seems to be released. Is it correct that this issue shows as "open"?

We as GPGTools would also like to see this addition being integrated into GnuPG, since we do plan to switch to keys.openpgp.org in the near future, as we have long been hoping for a key server with better performance and among other things email verification. Without this change, revocations would not work as expected in combination with hagrid however. Preferably of course in the 2.2.X branch.

Users keep showing up in our support, confused by this inconsistency. This problem continues in 2020. What's holding this back?

Hi Werner and thanks for looking into this.

ping, what's the status of this bug? it has been in testing for over one year. is that the correct status?

Hi Werner. Did you by any chance already find the time to look into the changes?

Just for the protocol: This fix made it into the 2.1.22 release. Thanks a lot! (bug has tag "gpg22" though)