git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [BUG] Failed to sign commit

From
Bryan Turner <bturner@atlassian.com>
Date
Jun 7, 2017, 20:41 UTC
Message-ID
<CAGyf7-GGo7VQX3pNVSOg6ZVOfipynxpHvHKWNfgvfDQ5ODcCtQ@mail.gmail.com>
In-Reply-To
<CAPMsMoCi4JRB7e6DLLOx+i-Gbfeh=EXeytWPn0WruOPJQZ0vow@mail.gmail.com>
Show 10 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.

Previous: pedro rijoNext: pedro rijo
Message 4 of 5 in “[BUG] Failed to sign commit”
  1. pedro rijoJun 7, 2017
  2. Kevin DaudtJun 7, 2017
  3. pedro rijoJun 7, 2017
  4. Bryan TurnerJun 7, 2017
  5. pedro rijoJun 9, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.