From: Jeff King <peff@peff.net>
To: Gary Yang <garyyang6@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: "secret key not available". "unable to sign the tag".
Date: Fri, 14 Nov 2008 22:57:43 -0500 [thread overview]
Message-ID: <20081115035743.GA19633@coredump.intra.peff.net> (raw)
In-Reply-To: <823128.71540.qm@web37902.mail.mud.yahoo.com>
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
next prev parent reply other threads:[~2008-11-15 3:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 23:28 "secret key not available". "unable to sign the tag" Gary Yang
2008-11-15 3:57 ` Jeff King [this message]
2008-11-17 0:16 ` Linus Torvalds
2008-11-18 16:55 ` Gary Yang
2008-11-18 16:57 ` Gary Yang
2008-11-18 1:59 ` Gary Yang
2008-11-18 4:21 ` Linus Torvalds
2008-11-18 20:22 ` Gary Yang
2008-11-18 20:26 ` Gary Yang
2008-11-18 21:20 ` Gary Yang
2008-11-19 15:42 ` Linus Torvalds
2008-11-19 16:54 ` Gary Yang
2010-02-04 11:44 ` SASh-4
[not found] <49236F67.6080807@pcharlan.com>
2008-11-19 2:19 ` Gary Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081115035743.GA19633@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=garyyang6@yahoo.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).