{"thread":{"id":"46131","subject":"[BUG] Failed to sign commit","startedAt":"2017-06-07T09:48:05Z","lastAt":"2017-06-09T13:06:08Z","messageCount":5,"participants":["pedro rijo","Kevin Daudt","Bryan Turner"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"321666","messageId":"CAPMsMoAYpS8QMrfyed5=XPWJLbV6=kMg5gp-2a75kWMpVD3D1A@mail.gmail.com","threadId":"46131","inReplyTo":null,"subject":"[BUG] Failed to sign commit","fromName":"pedro rijo","fromEmail":"pedrorijo91@gmail.com","sentAt":"2017-06-07T09:46:08Z","receivedAt":"2017-06-07T09:48:05Z","isPatch":false,"sender":{"key":"pedrorijo91@gmail.com","avatar":"https://gravatar.com/avatar/a3f4c97ae763402c3ffc08abfec39ef86f6040e34cc9c2a28d36ed10a7a70c91?d=mp&s=160"},"body":"Recently I've updated a bunch of stuff, including git and gpg. I'm using\n\n- mac OS 10.10.5\n- git 2.13.1\n- gpg (GnuPG) 2.1.21 / libgcrypt 1.7.7\n\nWhen I do\n\n$ git commit --allow-empty -v -m \"lol\"\nerror: gpg failed to sign the data\nfatal: failed to write commit object\n\nI tried the verbose flag hoping to have a better insight, but not very\nuseful. Not sure if it's a gpg problem, a git problem, or something\nelse.\n\nAny clue on how to debug the problem? Do you need any gpg output to\nbetter understand the problem?\n\nThanks,\nPedro\n"},{"id":"321669","messageId":"20170607103326.GB27719@alpha.vpn.ikke.info","threadId":"46131","inReplyTo":"CAPMsMoAYpS8QMrfyed5=XPWJLbV6=kMg5gp-2a75kWMpVD3D1A@mail.gmail.com","subject":"Re: [BUG] Failed to sign commit","fromName":"Kevin Daudt","fromEmail":"me@ikke.info","sentAt":"2017-06-07T10:33:26Z","receivedAt":"2017-06-07T10:33:48Z","isPatch":false,"sender":{"key":"me@ikke.info","avatar":"https://avatars.githubusercontent.com/u/135698?v=4"},"body":"On Wed, Jun 07, 2017 at 10:46:08AM +0100, pedro rijo wrote:\n> Recently I've updated a bunch of stuff, including git and gpg. I'm using\n> \n> - mac OS 10.10.5\n> - git 2.13.1\n> - gpg (GnuPG) 2.1.21 / libgcrypt 1.7.7\n> \n> When I do\n> \n> $ git commit --allow-empty -v -m \"lol\"\n> error: gpg failed to sign the data\n> fatal: failed to write commit object\n> \n> I tried the verbose flag hoping to have a better insight, but not very\n> useful. Not sure if it's a gpg problem, a git problem, or something\n> else.\n> \n> Any clue on how to debug the problem? Do you need any gpg output to\n> better understand the problem?\n> \n> Thanks,\n> Pedro\n\nGIT_TRACE=1 git commit --allow-empty -v -m \"lol\" might give some extra\nfeedback (ie, what gpg command git runs), and try to see if you can\nreplicate it.\n"},{"id":"321672","messageId":"CAPMsMoCi4JRB7e6DLLOx+i-Gbfeh=EXeytWPn0WruOPJQZ0vow@mail.gmail.com","threadId":"46131","inReplyTo":"20170607103326.GB27719@alpha.vpn.ikke.info","subject":"Re: [BUG] Failed to sign commit","fromName":"pedro rijo","fromEmail":"pedrorijo91@gmail.com","sentAt":"2017-06-07T10:39:17Z","receivedAt":"2017-06-07T10:40:08Z","isPatch":false,"sender":{"key":"pedrorijo91@gmail.com","avatar":"https://gravatar.com/avatar/a3f4c97ae763402c3ffc08abfec39ef86f6040e34cc9c2a28d36ed10a7a70c91?d=mp&s=160"},"body":"Thanks for the hint!\n\n$ GIT_TRACE=1 git commit --allow-empty -v -m \"lol\"\n11:37:24.594795 git.c:369               trace: built-in: git 'commit'\n'--allow-empty' '-v' '-m' 'lol'\n11:37:24.605842 run-command.c:369       trace: run_command: 'gpg'\n'--status-fd=2' '-bsau' '8AEC0DB537A9FC7E'\nerror: gpg failed to sign the data\nfatal: failed to write commit object\n\nIt seems more a gpg problem no? something not well configured after\nthe update perhaps?\n\n2017-06-07 11:33 GMT+01:00 Kevin Daudt <me@ikke.info>:\n> On Wed, Jun 07, 2017 at 10:46:08AM +0100, pedro rijo wrote:\n>> Recently I've updated a bunch of stuff, including git and gpg. I'm using\n>>\n>> - mac OS 10.10.5\n>> - git 2.13.1\n>> - gpg (GnuPG) 2.1.21 / libgcrypt 1.7.7\n>>\n>> When I do\n>>\n>> $ git commit --allow-empty -v -m \"lol\"\n>> error: gpg failed to sign the data\n>> fatal: failed to write commit object\n>>\n>> I tried the verbose flag hoping to have a better insight, but not very\n>> useful. Not sure if it's a gpg problem, a git problem, or something\n>> else.\n>>\n>> Any clue on how to debug the problem? Do you need any gpg output to\n>> better understand the problem?\n>>\n>> Thanks,\n>> Pedro\n>\n> GIT_TRACE=1 git commit --allow-empty -v -m \"lol\" might give some extra\n> feedback (ie, what gpg command git runs), and try to see if you can\n> replicate it.\n\n\n\n-- \nObrigado,\n\nPedro Rijo\n"},{"id":"321708","messageId":"CAGyf7-GGo7VQX3pNVSOg6ZVOfipynxpHvHKWNfgvfDQ5ODcCtQ@mail.gmail.com","threadId":"46131","inReplyTo":"CAPMsMoCi4JRB7e6DLLOx+i-Gbfeh=EXeytWPn0WruOPJQZ0vow@mail.gmail.com","subject":"Re: [BUG] Failed to sign commit","fromName":"Bryan Turner","fromEmail":"bturner@atlassian.com","sentAt":"2017-06-07T20:41:36Z","receivedAt":"2017-06-07T20:41:43Z","isPatch":false,"sender":{"key":"bturner@atlassian.com","avatar":"https://gravatar.com/avatar/16bcf3167981c1ef7c804e502642366d888a35b0d0b0a4ca01fdc442aa1acb1e?d=mp&s=160"},"body":"> $ GIT_TRACE=1 git commit --allow-empty -v -m \"lol\"\n> 11:37:24.594795 git.c:369               trace: built-in: git 'commit'\n> '--allow-empty' '-v' '-m' 'lol'\n> 11:37:24.605842 run-command.c:369       trace: run_command: 'gpg'\n> '--status-fd=2' '-bsau' '8AEC0DB537A9FC7E'\n> error: gpg failed to sign the data\n> fatal: failed to write commit object\n>\n> It seems more a gpg problem no? something not well configured after\n> the update perhaps?\n\nHave you tried running `export GPG_TTY=$(tty)` before running `git\ncommit`? I had a similar gpg error that was solved by that.\n"},{"id":"321825","messageId":"CAPMsMoBXTL5=GC2mBH6vAFOO3dca1WpF3ouDNPcSzA-pUgE-CA@mail.gmail.com","threadId":"46131","inReplyTo":"CAGyf7-GGo7VQX3pNVSOg6ZVOfipynxpHvHKWNfgvfDQ5ODcCtQ@mail.gmail.com","subject":"Re: [BUG] Failed to sign commit","fromName":"pedro rijo","fromEmail":"pedrorijo91@gmail.com","sentAt":"2017-06-09T13:05:21Z","receivedAt":"2017-06-09T13:06:08Z","isPatch":false,"sender":{"key":"pedrorijo91@gmail.com","avatar":"https://gravatar.com/avatar/a3f4c97ae763402c3ffc08abfec39ef86f6040e34cc9c2a28d36ed10a7a70c91?d=mp&s=160"},"body":"as much cliché as it may seem, GPG was with some strange behaviour,\nkilling the agent and starting again make it work with no problems....\n\nThanks for the help\n\n2017-06-07 21:41 GMT+01:00 Bryan Turner <bturner@atlassian.com>:\n>> $ GIT_TRACE=1 git commit --allow-empty -v -m \"lol\"\n>> 11:37:24.594795 git.c:369               trace: built-in: git 'commit'\n>> '--allow-empty' '-v' '-m' 'lol'\n>> 11:37:24.605842 run-command.c:369       trace: run_command: 'gpg'\n>> '--status-fd=2' '-bsau' '8AEC0DB537A9FC7E'\n>> error: gpg failed to sign the data\n>> fatal: failed to write commit object\n>>\n>> It seems more a gpg problem no? something not well configured after\n>> the update perhaps?\n>\n> Have you tried running `export GPG_TTY=$(tty)` before running `git\n> commit`? I had a similar gpg error that was solved by that.\n\n\n\n-- \nObrigado,\n\nPedro Rijo\n"}]}