On Tue, Apr 26, 2016 at 01:14:40PM -0400, Leo Famulari wrote: > On Tue, Apr 26, 2016 at 05:03:18PM +0300, Efraim Flashner wrote: > > * gnu/packages/gnupg.scm (pinentry): Rename pinentry-gtk, inherit from > > pinentry. > > [arguments]: Add pinentry-tty flag. > > [inputs]: Use gtk+-2, glib for pinentry-gtk2 only. > > [description]: Modify description based on inputs. > > --- > > gnu/packages/gnupg.scm | 22 +++++++++++++++++----- > > 1 file changed, 17 insertions(+), 5 deletions(-) > > > > diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm > > index d447007..71f6ece 100644 > > --- a/gnu/packages/gnupg.scm > > +++ b/gnu/packages/gnupg.scm > > @@ -580,21 +580,33 @@ including tools for signing keys, keyring analysis, and party preparation. > > (base32 > > "1cp7wjqr6nx31mdclr61s2h84ijqjl0ph99kgj4vyawpjj1j1633")))) > > (build-system gnu-build-system) > > + (arguments > > + `(#:configure-flags '("--enable-pinentry-tty"))) > > Won't pinentry-gtk2 get configured with this? Can you change > pinentry-gtk2 so that it doesn't get this flag? It will get the flag the way its currently configured, but pinentry-gtk2 will still be the default method. The real difference (if I understand it correctly) is that now if you ssh into the box and you trigger pinentry it should now work. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted