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

Re: "secret key not available". "unable to sign the tag".

From
GYGary Yang <garyyang6@yahoo.com>
Date
Nov 18, 2008, 20:26 UTC
Message-ID
<810496.66936.qm@web37903.mail.mud.yahoo.com>
In-Reply-To
<832452.93473.qm@web37901.mail.mud.yahoo.com>
Here are the errors I got:
git tag -s my-second-tag

gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information gpg: skipped `Gary Yang <garyyang6@yahoo.com>': secret key not available gpg: signing failed: secret key not available error: gpg failed to sign the tag fatal: unable to sign the tag

Thanks,
Gary
--- On Tue, 11/18/08, Gary Yang <garyyang6@yahoo.com> wrote:
Show 110 quoted lines
> From: Gary Yang <garyyang6@yahoo.com>
> Subject: Re: "secret key not available". "unable to sign the tag".
> To: "Jeff King" <peff@peff.net>, "Linus Torvalds" <torvalds@linux-foundation.org>
> Cc: git@vger.kernel.org
> Date: Tuesday, November 18, 2008, 12:22 PM
> All,
> 
> I really need to tag my source code. But, somehow I am not
> able. Can someone help?
> 
> Thanks in advance!
> 
> 
> Gary
> 
> 
> 
> --- On Tue, 11/18/08, Gary Yang <garyyang6@yahoo.com>
> wrote:
> 
> > From: Gary Yang <garyyang6@yahoo.com>
> > Subject: Re: "secret key not available".
> "unable to sign the tag".
> > To: "Jeff King" <peff@peff.net>,
> "Linus Torvalds"
> <torvalds@linux-foundation.org>
> > Cc: git@vger.kernel.org
> > Date: Tuesday, November 18, 2008, 8:57 AM
> > Hi Linus,
> > 
> > I do not understand your email. I used the command,
> git
> > config --global user.email garyyang6@yahoo.com. But, I
> still
> > got the same error. Do you have any idea?
> > 
> > Thank you,
> > 
> > 
> > Gary
> > 
> > 
> > --- On Sun, 11/16/08, Linus Torvalds
> > <torvalds@linux-foundation.org> wrote:
> > 
> > > From: Linus Torvalds
> > <torvalds@linux-foundation.org>
> > > Subject: Re: "secret key not
> available".
> > "unable to sign the tag".
> > > To: "Jeff King" <peff@peff.net>
> > > Cc: "Gary Yang"
> <garyyang6@yahoo.com>,
> > git@vger.kernel.org
> > > Date: Sunday, November 16, 2008, 4:16 PM
> > > On Fri, 14 Nov 2008, Jeff King wrote:
> > > > 
> > > > You need to tell git who you are, since it
> is
> > unable
> > > to deduce it from
> > > > doing host lookups. Try:
> > > > 
> > > >   git config --global user.email
> > garyyang6@yahoo.com
> > > > 
> > > > or whatever email address you used when you
> > created
> > > the key, and then
> > > > gpg should find it appropriately.
> > > 
> > > Side note: sometimes you might want to use a
> different
> > key
> > > than the one 
> > > you use for authorship. Then you can use
> > > 
> > > 	[user]
> > > 		SigningKey = key
> > > 
> > > (or "git config user.signingkey xyz" if
> you
> > > don't want to edit the 
> > > config file manually). 
> > > 
> > > This can be especially useful if you use
> different
> > keys for
> > > different 
> > > projects, even if you want to be known under the
> same
> > name
> > > in both. Or 
> > > because you want to have the local hostname in
> your
> > commit
> > > logs, but your 
> > > gpg key is using some externally visible
> > > "official" email address.
> > > 
> > > 			Linus
> 
> 
>       
> --
> To unsubscribe from this list: send the line
> "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
Previous: Gary YangNext: Gary Yang
Message 2 of 6 in “Re: "secret key not available". "unable to sign the tag".”
  1. Gary YangNov 18, 2008
  2. Gary YangNov 18, 2008
  3. Gary YangNov 18, 2008
  4. Linus TorvaldsNov 19, 2008
  5. Gary YangNov 19, 2008
  6. SASh-4Feb 4, 2010

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.