iirc, we once disabled the trustdb check because it was run for each imported certificate which took long and was superfluous die to changes introduced by the next certificates. GPGME has a "no-auto-check-trustdb" flag to allow for this.
See T6261

@TobiasFella: This is on purpose: The key might be expired because the user does not have the primary address anymore and thus it makes no sense to show the name. Anyway the listing of the name is more a convenience thing and it might be better if the frontend takes it from its own cache. But it is pretty old code and things and ideas may have changed meanwhile.

The data looks garbled:

gpg makes it pretty hard to delete a secret key; thus having a (user settable) option in Kleopatra makes a lot of sense to me.

In case you run into problems installing the bzip2 part w/o root rights, you need to apply rGc333e9dad66 to set the PREFIX make variable also for bzip2.

That is probably right for gpgme as used by kleopatra. However in gnupg we need to switch utf8 on and off.

rere 2: I agree as long as the expired certs are order behind regular certs.

Noteworthy changes in version 1.3.1 (2024-07-03)

Backported to 2.4. Options are now listed with gpgconf.

Yes, the SO number changed. Before that you had run the test with an old version of the library or maybe the current one depending on your system. However, a changed SO number means that you have can have two versions of the library installed and they don't alias them with symlinks. We rarely update SO numbers but int he libassuan case we did it because technically we had a minor ABI change but GnuPG and Cie. are not affected; we did it anyway to be correct.

What you should is to to run

Did you used the speedo build method? Did you install libassuan first?

Our Makefile does not use -Wincompatible-pointer-types for a reason. Please build gpgme only the standard way, i.e. by using ./autogen.sh --build-w32. Keep in mind that C is an entire different language than C++.

Thanks.