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

Re: Lack of debug info from git commit -vvv -S -am "..."

From
Duy Nguyen <pclouds@gmail.com>
Date
Dec 30, 2018, 05:07 UTC
Message-ID
<CACsJy8COCZan=UVjK6P=WXdtK+pD=_PY-HhEZzEOhf=6kUicXw@mail.gmail.com>
In-Reply-To
<CAH8yC8=zaL3ETrOSk_3xQobfG-z2VLMsGn8O-q0zCaqw6C_Bqg@mail.gmail.com>
On Sun, Dec 30, 2018 at 7:38 AM Jeffrey Walton <noloader@gmail.com> wrote:
Show 12 quoted lines
>
> I'm trying to determine why a new installation of GnuPG is having
> trouble. The new install is in /usr/local. The other install is from
> the distro and is OK.
>
> Here's the new installation error message:
>
>     $ git commit -vvv -S -am "Update GnuPG recipe"
>     error: gpg failed to sign the data
>     fatal: failed to write commit object
>
> How can I obtain more information from git commit?
try
$ GIT_TRACE=1 git commit ...

That should give you more info and the exact gnupg command to execute should be there too

-- 
Duy
Previous: Jeffrey Walton
Message 2 of 2 in “Lack of debug info from git commit -vvv -S -am "..."”
  1. Jeffrey WaltonDec 29, 2018
  2. Duy NguyenDec 30, 2018

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.