git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Problem signing a tag

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 5, 2009, 20:09 UTC
Message-ID
<7vy6mk91ig.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4AF28CE4.5000906@drmicha.warpmail.net>
Michael J Gruber <git@drmicha.warpmail.net> writes:
Show 10 quoted lines
> Dig dig dig... gpg exits with 2 in a lot of cases, one would need to
> parse fd-error to find out more. But it also looks as if gpg exits
> normally with a good passphrase. So I tried, and at least with gpg 1.4.9
> and git 1.6.5.2 I can sign tags with "use-agent" and without a running
> agent: I get asked for the passphrase (after reporting the agent MIA),
> and everything's fine.
>
> My gpg returns 0 in this case; it returns 2 only if I don't enter the
> passphrase. So, this seems to depend on the version of gpg. Or on
> entering the correct passphrase ;)

If the problematic gpg that gives 2 is older than yours, the situation looks to me that "exiting 2 when failed to contact agent but got a good passphrase some other way and successfully signed" was diagnosed as a bug and then fixed in gpg. If that is the case can we find out which version that fix is in, and add an entry to FAQ to help next person who will be hit by this when using "tag -s"?

Previous: Joshua J. KuglerNext: Michael J Gruber
Message 8 of 10 in “Problem signing a tag”
  1. Joshua J. KuglerNov 3, 2009
  2. Alex RiesenNov 3, 2009
  3. Joshua J. KuglerNov 3, 2009
  4. Michael J GruberNov 4, 2009
  5. Joshua J. KuglerNov 4, 2009
  6. Michael J GruberNov 5, 2009
  7. Joshua J. KuglerNov 5, 2009
  8. Junio C HamanoNov 5, 2009
  9. Michael J GruberNov 6, 2009
  10. Joshua J. KuglerNov 9, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.