From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.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: Wed, 27 Jul 2016 11:54:05 +0200 [thread overview]
Message-ID: <20160727115405.704f02ac@scratchpost.org> (raw)
In-Reply-To: <87poq016rt.fsf@gnu.org>
Hi Ludo,
> My ~/.gnupg/gpg-agent.conf file reads this:
>
> --8<---------------cut here---------------start------------->8---
> pinentry-program /home/ludo/.guix-profile/bin/pinentry-gtk-2
> --8<---------------cut here---------------end--------------->8---
Yes, the file didn't exist. I created it and it works now.
I did install the pinentry package, though.
Do you think it would make sense to put this in the skeleton for new user accounts?
It wouldn't matter if it's were not installed then - then the user will get an error message and would install it (hopefully). But then it would work.
next prev parent reply other threads:[~2016-07-27 9:55 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160727115405.704f02ac@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=24076@debbugs.gnu.org \
--cc=ludo@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 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.