Re: [BUG] Failed to sign commit

From: pedro rijo <pedrorijo91@gmail.com>
Date: Jun 9, 2017, 13:05 UTC
Message-ID: <CAPMsMoBXTL5=GC2mBH6vAFOO3dca1WpF3ouDNPcSzA-pUgE-CA@mail.gmail.com>
In-Reply-To: <CAGyf7-GGo7VQX3pNVSOg6ZVOfipynxpHvHKWNfgvfDQ5ODcCtQ@mail.gmail.com>

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>:

Show 13 quoted lines

>> $ 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