Here is my attempt:

Additionally to performing the lookup also for OpenPGP cards the status messages that are emitted during the lookup are now shown in the status bar instead of with a label above the key list.

Use of execve is better (avoiding use of environ).

This ticket got superseded by T7262: gpgme: Move C++ bindings, Qt bindings and Python bindings to separate git repositories.

Since VSD 3.3 will likely include this change in gpgme I add the vsd33 tag.

In T4060#190972, @werner wrote:

We need a way to pass --known-notation to gpgme_op_verify

We need a way to pass --known-notation to gpgme_op_verify

I asked you to write to the mailing list instead of filing a bug report. A mailing list has a far wider audience than a single bug report. Our bug tracker is not a help forum or a place to ask questions.

Fixed in: rA69069bc63e6b: Remove an declaration for an unused function

I re-consider. Adding arguments to existing gcry_kem_keypair is not good since it introduces API break.
Instead, I add gcry_kem_genkey with additional arguments (which can be used for deterministic key generation).

Wouldn't anyone suspect that you are in the habit of dispensing the ''Invalid'' label without discernment for reports that, however, have no basis as such? But what on earth could you possibly be trying to achieve by acting in this way?

In T7283#190941, @gniibe wrote:

I can replicate the problem.

The cause of this is that when it's comes with loopback mode, gpg-agent inquires back to the frontend and the buffer overwritten, which results parsing the line wrong.
I'm going to fix.

In T7283#190901, @werner wrote:

y38k problems with some frontends are known for some 32 bit platforms.

Please write a proper bug report and don't expect us to read a reddit thread.

I can replicate the problem.

FWIW: the encryption part of the ADSK feature has been released with

Fixed.

Will be updated eventually. Thanks for reporting.

Please use the mailing list for such questions.

I can reproduce this: It works with setuptools 72.1.0 and it fails with setuptools 72.2.0.

y38k problems with some frontends are known for some 32 bit platforms.

Use --enable-large-data-tests with configure and go out for a real long lunch