From: Danny Milosavljevic <dannym@scratchpost.org>
To: 24076@debbugs.gnu.org
Subject: bug#24076: gnupg [-agent]: when signing [commits], it claims that there is no pinentry - but there is
Date: Tue, 26 Jul 2016 18:05:07 +0200 [thread overview]
Message-ID: <20160726180507.21e5e8e0@scratchpost.org> (raw)
dannym@dayas ~/src/guix$ strace -f git commit -S -m "x" gnu/packages/databases.scm 2>&1 |grep pinentry
[pid 32548] write(4, "OPTION allow-pinentry-notify", 28) = 28
[pid 32548] read(4, "ERR 67108949 No pinentry <GPG Ag"..., 1002) = 37
[pid 32548] write(2, "gpg: signing failed: No pinentry", 32gpg: signing failed: No pinentry) = 32
[pid 32548] write(2, "gpg: signing failed: No pinentry", 32gpg: signing failed: No pinentry) = 32
dannym@dayas ~$ which pinentry
/home/dannym/.guix-profile/bin/pinentry
dannym@dayas ~$ pinen<TAB>
pinentry pinentry-curses pinentry-gtk-2 pinentry-tty
dannym@dayas ~$ pinentry
OK Pleased to meet you
next reply other threads:[~2016-07-26 16:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 16:05 Danny Milosavljevic [this message]
2016-07-26 20:30 ` bug#24076: gnupg [-agent]: when signing [commits], it claims that there is no pinentry - but there is 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
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160726180507.21e5e8e0@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=24076@debbugs.gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).