Thread (7 messages) flat view 7 messages, 3 authors, 2016-06-15

Re: Problem signing a tag

From: Joshua J. Kugler <hidden>
Date: 2016-06-15 22:47:40

On Wednesday 04 November 2009, Michael J Gruber said something like:
quoted
So, the docs consider 2 a fatal error, even though it appears it
isn't. It seems that
http://github.com/git/git/blob/a6dbf8814f433a7fbfa9cde6333c98019f6d
b1e4/builtin-tag.c#L202 needs to be patched to something along the
lines of:

rv = finish_command(&gpg)
if ((rv && rv !=2)  || !len || len < 0)

Probably digging in to the gpg source code to figure out what
errors are and aren't fatal would be in order.

Thanks again for your help! Glad to know what I needed to do to
sign my tags!
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 ;)

Michael
That is weird.  Because when working from the prompt (with agent MIA), 
gpg 1.4.9, it would accept my pass phrase, and would print the 
signature (either binary or ascii armored), but it will still exit with 
2.  I don't understand it.  I'll pop on #gnupg tomorrow and ask about 
it.

Thanks again for your help with this!

j

-- 
Joshua Kugler
Part-Time System Admin/Programmer
http://www.eeinternet.com
PGP Key: http://pgp.mit.edu/  ID 0x14EA086E
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help