Je 18 dec 22:50 skribis Andreas:
> On Wed, Dec 18, 2019 at 10:41:27PM +0100, Marco van Hulten wrote:
> > Do I need to do any more actions accept for 'guix package -i gnupg
> > pinentry'?  
> 
> I also have a file .gnupg/gpg-agent.conf in my home directory
> containing the following lines:
> 
> default-cache-ttl 300
> max-cache-ttl 3600
> pinentry-program /home/USERNAME/.guix-profile/bin/pinentry-curses

Thank you, Andreas and Gábor, very useful to know that pinentry-program
should be set.  I did so:

$ file $(realpath $(grep ^pinentry-program ~/.gnupg/gpg-agent.conf | awk '{print $2}'))
/gnu/store/12gagy0ql4v7qlv9px54lz5fy4d7gff9-pinentry-tty-1.1.0/bin/pinentry-tty:
ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked,
interpreter /gnu/store/ahqgl4h89xqj695lgqvsaf6zh2nhy4pj-glibc-2.29/lib/ld-linux-x86-64.so.2,
for GNU/Linux 2.6.32, not stripped

Importing a public and private key pair, following [1], worked properly
now, but it still complains when decrypting a file.

[1]: https://www.debuntu.org/how-to-importexport-gpg-key-pair/

To be sure, if I now try to remove the key, 'gpg --delete-key publiko',
it says that I need to use option "--delete-secret-keys" to delete the
private key first.  So it appears to be really there.  However,

    $ date | gpg -e > jadaja.gpg
    gpg: encrypted with 4096-bit RSA key, ID 54AE7D44B93BDBDF, created 2019-05-30
          "Marco van Hulten (publiko) <marco@hulten.org>"
    gpg: public key decryption failed: No pinentry
    gpg: decryption failed: No secret key

I tried killing gpg-agent to be sure it uses the current configuration,
but again it complains about pinentry.

Apropos, I this e-mail is signed with this very key.

—Marco