From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: 24076@debbugs.gnu.org
Subject: bug#24076: gnupg [-agent]: when signing [commits], it claims that there is no pinentry - but there is
Date: Fri, 14 Oct 2016 15:16:52 +0200 [thread overview]
Message-ID: <871szjax4r.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPM5UcDkkz0h7MLKK2GJPn4bY6GyGg5W7zMGA43oHC-nfQ@mail.gmail.com> (Federico Beffa's message of "Fri, 14 Oct 2016 08:45:28 +0200")
Federico Beffa <beffa@ieee.org> skribis:
> Note that installing 'gnupg' doesn't automatically bring in
> 'pinentry'. For this reason installing 'gnupg' doesn't work out of the
> box as a user would expect:
>
> gpg: agent_genkey failed: No pinentry
> Key generation failed: No pinentry
I agree that this is a problem. A fix that would work is the 2nd option
outlined at:
https://lists.gnu.org/archive/html/bug-guix/2016-07/msg00092.html
Haven’t taken the time to look into it yet!
Ludo’.
next prev parent reply other threads:[~2016-10-14 13:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 16:05 bug#24076: gnupg [-agent]: when signing [commits], it claims that there is no pinentry - but there is Danny Milosavljevic
2016-07-26 20:30 ` Ludovic Courtès
2016-07-27 9:54 ` Danny Milosavljevic
2016-07-27 11:01 ` Ludovic Courtès
2016-07-28 9:56 ` Alex Kost
2016-07-28 11:52 ` Ludovic Courtès
2016-07-28 12:04 ` Danny Milosavljevic
2016-07-28 17:58 ` Alex Kost
2020-03-26 12:09 ` Ludovic Courtès
2020-03-27 20:02 ` Leo Famulari
2016-10-14 6:45 ` Federico Beffa
2016-10-14 13:16 ` Ludovic Courtès [this message]
2019-07-22 11:44 ` Robert Vollmert
2020-03-27 22:48 ` bug#24076: [PATCH] gnu: GnuPG: Really use ~/.guix-profile/bin/pinentry by default Leo Famulari
2020-03-29 14:57 ` Ludovic Courtès
2020-03-29 19:27 ` Leo Famulari
2021-04-22 21:49 ` bug#24076: gnupg [-agent]: when signing [commits], it claims that there is no pinentry - but there is Alexandre Hannud Abdo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871szjax4r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=24076@debbugs.gnu.org \
--cc=beffa@ieee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.