configure warnings and errors upon ./configure for Pinentry v0.9.7

Stephan Beck stebe at
Wed Nov 23 17:39:00 CET 2016

Peter Lebbing:
> On 23/11/16 11:14, Stephan Beck wrote:
>> [...] and properly symlink
>> /usr/bin/pinentry to the pinentry-curses you actually would like to use
>> if you are using text-mode only, I don't know why it should not work.
[...]So by installing the Debian pinentry-curses
> package, David should already have a /usr/bin/pinentry.
Yes, it has helped, thanks. But I looked at one of the OP's previous
mail and was confirmed.

> I looked for a GUI platform but had no idea what it's called where to
> find it and why I need a GUI if I plan on using purely command line
> interface.

So, I am puzzled by the fact that he switched to GUI pinentry that
quickly, without providing more info on the error, so I proposed to get
the maximum amount of info possible using the debug-level flag.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x4218732B.asc
Type: application/pgp-keys
Size: 4089 bytes
Desc: not available
URL: </pipermail/attachments/20161123/fcc4693e/attachment-0001.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20161123/fcc4693e/attachment-0001.sig>

More information about the Gnupg-users mailing list