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

[Gary Yang <garyyang6@yahoo.com>]

Jeff King,

I followed your instruction. But, I still got error when I tag the code. Can you please tell me why?

>   git config --global user.email garyyang6@yahoo.com

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 Fri, 11/14/08, Jeff King <peff@peff.net> wrote:

> From: Jeff King <peff@peff.net>
> Subject: Re: "secret key not available". "unable to sign the tag".
> To: "Gary Yang" <garyyang6@yahoo.com>
> Cc: git@vger.kernel.org
> Date: Friday, November 14, 2008, 7:57 PM
> On Fri, Nov 14, 2008 at 03:28:44PM -0800, Gary Yang wrote:
> 
> > I got errors and warnings when I used "git tag -s
> my-tag". It says,
> > "secret key not available". "unable to
> sign the tag". 
> 
> Probably because it can't find your secret key, like it
> says.
> 
> > gpg: please see http://www.gnupg.org/faq.html for more
> information
> > gpg: skipped `Gary Yang
> <gyang@linux123.(none)>': secret key not available
> > gpg: signing failed: secret key not available
> > error: gpg failed to sign the tag
> > fatal: unable to sign the tag
> > 
> > I ran "gpg --gen-key" and generated keypair.
> But, still got the same
> > error. Please help.
> 
> Did the key you generated have the email address
> "gyang@linux123.(none)"? If not, then that is
> your problem.
> 
> 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.
> 
> -Peff
> --
> 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