[BUG] Failed to sign commit

[BUG] Failed to sign commit

[pedro rijo]

Recently I've updated a bunch of stuff, including git and gpg. I'm using

- mac OS 10.10.5
- git 2.13.1
- gpg (GnuPG) 2.1.21 / libgcrypt 1.7.7

When I do

$ git commit --allow-empty -v -m "lol"
error: gpg failed to sign the data
fatal: failed to write commit object

I tried the verbose flag hoping to have a better insight, but not very
useful. Not sure if it's a gpg problem, a git problem, or something
else.

Any clue on how to debug the problem? Do you need any gpg output to
better understand the problem?

Thanks,
Pedro

Re: [BUG] Failed to sign commit

[Kevin Daudt]

On Wed, Jun 07, 2017 at 10:46:08AM +0100, pedro rijo wrote:
> Recently I've updated a bunch of stuff, including git and gpg. I'm using
> 
> - mac OS 10.10.5
> - git 2.13.1
> - gpg (GnuPG) 2.1.21 / libgcrypt 1.7.7
> 
> When I do
> 
> $ git commit --allow-empty -v -m "lol"
> error: gpg failed to sign the data
> fatal: failed to write commit object
> 
> I tried the verbose flag hoping to have a better insight, but not very
> useful. Not sure if it's a gpg problem, a git problem, or something
> else.
> 
> Any clue on how to debug the problem? Do you need any gpg output to
> better understand the problem?
> 
> Thanks,
> Pedro

GIT_TRACE=1 git commit --allow-empty -v -m "lol" might give some extra
feedback (ie, what gpg command git runs), and try to see if you can
replicate it.

Re: [BUG] Failed to sign commit

[pedro rijo]

Thanks for the hint!

$ GIT_TRACE=1 git commit --allow-empty -v -m "lol"
11:37:24.594795 git.c:369               trace: built-in: git 'commit'
'--allow-empty' '-v' '-m' 'lol'
11:37:24.605842 run-command.c:369       trace: run_command: 'gpg'
'--status-fd=2' '-bsau' '8AEC0DB537A9FC7E'
error: gpg failed to sign the data
fatal: failed to write commit object

It seems more a gpg problem no? something not well configured after
the update perhaps?

2017-06-07 11:33 GMT+01:00 Kevin Daudt <me@ikke.info>:
> On Wed, Jun 07, 2017 at 10:46:08AM +0100, pedro rijo wrote:
>> Recently I've updated a bunch of stuff, including git and gpg. I'm using
>>
>> - mac OS 10.10.5
>> - git 2.13.1
>> - gpg (GnuPG) 2.1.21 / libgcrypt 1.7.7
>>
>> When I do
>>
>> $ git commit --allow-empty -v -m "lol"
>> error: gpg failed to sign the data
>> fatal: failed to write commit object
>>
>> I tried the verbose flag hoping to have a better insight, but not very
>> useful. Not sure if it's a gpg problem, a git problem, or something
>> else.
>>
>> Any clue on how to debug the problem? Do you need any gpg output to
>> better understand the problem?
>>
>> Thanks,
>> Pedro
>
> GIT_TRACE=1 git commit --allow-empty -v -m "lol" might give some extra
> feedback (ie, what gpg command git runs), and try to see if you can
> replicate it.



-- 
Obrigado,

Pedro Rijo

Re: [BUG] Failed to sign commit

[Bryan Turner]

> $ GIT_TRACE=1 git commit --allow-empty -v -m "lol"
> 11:37:24.594795 git.c:369               trace: built-in: git 'commit'
> '--allow-empty' '-v' '-m' 'lol'
> 11:37:24.605842 run-command.c:369       trace: run_command: 'gpg'
> '--status-fd=2' '-bsau' '8AEC0DB537A9FC7E'
> error: gpg failed to sign the data
> fatal: failed to write commit object
>
> It seems more a gpg problem no? something not well configured after
> the update perhaps?

Have you tried running `export GPG_TTY=$(tty)` before running `git
commit`? I had a similar gpg error that was solved by that.

Re: [BUG] Failed to sign commit

[pedro rijo]

as much cliché as it may seem, GPG was with some strange behaviour,
killing the agent and starting again make it work with no problems....

Thanks for the help

2017-06-07 21:41 GMT+01:00 Bryan Turner <bturner@atlassian.com>:
>> $ GIT_TRACE=1 git commit --allow-empty -v -m "lol"
>> 11:37:24.594795 git.c:369               trace: built-in: git 'commit'
>> '--allow-empty' '-v' '-m' 'lol'
>> 11:37:24.605842 run-command.c:369       trace: run_command: 'gpg'
>> '--status-fd=2' '-bsau' '8AEC0DB537A9FC7E'
>> error: gpg failed to sign the data
>> fatal: failed to write commit object
>>
>> It seems more a gpg problem no? something not well configured after
>> the update perhaps?
>
> Have you tried running `export GPG_TTY=$(tty)` before running `git
> commit`? I had a similar gpg error that was solved by that.



-- 
Obrigado,

Pedro Rijo