Your message dated Tue, 24 Feb 2009 11:09:11 +0000
with message-id
<[email protected]>
and subject line Re: Bug#507642: [[email protected]: Bug#507642: Doesn't work with
gpg-agent using pinentry-curses]
has caused the Debian Bug report #507642,
regarding Doesn't work with gpg-agent using pinentry-curses
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
507642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507642
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-core
Version: 1:1.6.0.2-1
Severity: normal
Hi there,
If I:
git tag -u 2B0920C0 -m 'Debian release 0.5.7-1' debian/0.5.7-1
in the libv4l git tree, I get:
Vous avez besoin d'une phrase de passe pour déverrouiller la
clé secrète pour l'utilisateur: « Loïc Minier (lool) <[email protected]> »
clé de 1024 bits DSA, ID 2B0920C0, créée le 2003-02-03
gpg: annulé par l'utilisateur
gpg: « 2B0920C0 » a été ignoré: mauvaise phrase de passe
gpg: signing failed: mauvaise phrase de passe
error: gpg failed to sign the tag
fatal: unable to sign the tag
("Bad passphrase" because it didn't get any passphrase from the agent)
This is because gpg asks gpg-agent for the passphrase which starts
pinentry-curses to prompt me for the passphrase, but git is not passing
stdin / stdout, so pinentry-curses can't prompt / output anything.
See #507479 for a similar issue which affected debsign.
You can reproduce my setup by installing gnupg-agent, setting use-agent
in ~/.gnupg/gpg.conf and setting "pinentry-program
/usr/bin/pinentry-curses" in ~/.gnupg/gpg-agent.conf (NB: /usr/bin is
required).
If I use pinentry-gtk2 under Xorg, it works fine.
Note that pinentry-qt/pinentry-gtk2 will fallback to curses if DISPLAY
isn't set.
Bye
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.27-1-686 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages git-core depends on:
ii libc6 2.7-16 GNU C Library: Shared libraries
ii libcurl3-gnutls 7.18.2-7 Multi-protocol file transfer libra
ii libdigest-sha1-perl 2.11-2+b1 NIST SHA-1 message digest algorith
ii liberror-perl 0.17-1 Perl module for error/exception ha
ii libexpat1 2.0.1-4 XML parsing C library - runtime li
ii perl-modules 5.10.0-18 Core Perl modules
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages git-core recommends:
ii less 418-1 Pager program similar to more
ii openssh-client [ssh-client] 1:5.1p1-4 secure shell client, an rlogin/rsh
ii patch 2.5.9-5 Apply a diff file to an original
ii rsync 3.0.4-3 fast remote file copy program (lik
Versions of packages git-core suggests:
pn git-arch <none> (no description available)
ii git-cvs 1:1.6.0.2-1 fast, scalable, distributed revisi
pn git-daemon-run <none> (no description available)
ii git-doc 1:1.6.0.2-1 fast, scalable, distributed revisi
ii git-email 1:1.6.0.2-1 fast, scalable, distributed revisi
ii git-gui 1:1.6.0.2-1 fast, scalable, distributed revisi
ii git-svn 1:1.6.0.2-1 fast, scalable, distributed revisi
ii gitk 1:1.6.0.2-1 fast, scalable, distributed revisi
pn gitweb <none> (no description available)
-- no debconf information
--
Loïc Minier
--- End Message ---
--- Begin Message ---
On Mon, Feb 23, 2009 at 08:22:40PM +0100, Loïc Minier wrote:
> On Mon, Feb 23, 2009, Gerrit Pape wrote:
> > Hi, please see below and
> > http://thread.gmane.org/gmane.comp.version-control.git/110838
> >
> > Do you agree that git doesn't need to change in this aspect?
>
> Oh, didn't know about GPG_TTY; thanks a lot for your efforts in writing
> that patch, and sorry for not configuring gpg-agent as it intended to
> be.
>
> Apologies for the wasted efforts then.
No problem.
> I don't mind setting GPG_TTY if that's the recommended way and will do
> so; as a result, I guess I don't care whether you fix the behavior when
> GPG_TTY isn't set.
Regards, Gerrit.
--- End Message ---
