Done in 2.2 and 2.3. The issuer certificate thing is a real error message and thus it should be printed.

Thanks for the report. Frankly the curses pinentries are not that widely tested.

Ingo, can you take care of this one?

With 2.2 the second works if the first passphrase prompt was canceled. Test invocation:

The configure run tells you what libraries are missing - none in your case. However, something is wrong with your development setup: The configure run detected libksba but cc compiler did not found it anymore. Check that you don't have any special envvars set etc. What is the actual compiler command which failed (make sure not to pass V=0 to make for this).

Note that the backlog at https://dev.gnupg.org/tag/gpg23/ has quite some items and it is not yet clear which we will implement/fix first.

Plesae run gpg with the option --verbose and put

Thanks. A few hours too late for 1.9.2.

Backport was done with commit rC1d312bc65846 (for unknown reasons it did not show up in the list of bugs related to this bug; I added it by hand). Fix will go into 1.8.8.

The mix up of external patches and commits makes it not easy to see what has been fixed. AFAICS rC3d095206c30d fixes the last bug mentioned by @ballapete on Jan 26.

Fixed with rCa5799f1618aaf1bbb52e7e121275228dd4a3ac8b

There is a message telling you what is missing. Thus I can not consider this a bug. There are just too many dependencies which are required for cross-compiling that the README can only tell about those which we don't expect to be installed on a developer's box.

They are mandatory for gnupg but not for Libgcrypt and Libgpg-error. I guess we can fix that.

This does not look like a bug report. Please ask on a mailing list for help.

There is still useful software working only with 2.7. So it is not the time to drop this.

A page feed character is a very common and useful control character. In fact Emacs knows how to jump page by page.

A beta release is available as https://gnupg.org/ftp/gcrypt/alpha/libgcrypt/libgcrypt-1.9.2-beta16.tar.bz2 (https://gnupg.org/ftp/gcrypt/alpha/libgcrypt/libgcrypt-1.9.2-beta16.tar.bz2.sig).

How does it come that you have a Linux kernel without threads? Or maybe the better question is why does libc not support threads?

For 2.3.0 we won't be able to fix all bugs./feature requests. Instead we l will solve that in the 2.3 series.