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 <btur...@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
