From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Aubrey <aubreylee@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Newbie question: git tag failure
Date: Thu, 2 Mar 2006 16:54:18 +0100 [thread overview]
Message-ID: <20060302155418.GZ19232@lug-owl.de> (raw)
In-Reply-To: <6d6a94c50603020751v4bb96b75q1686d36b32e2c40f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
On Thu, 2006-03-02 23:51:04 +0800, Aubrey <aubreylee@gmail.com> wrote:
> aubrey@linux:~/local/mygit>git tag -u
> 43368b967bd838292b8cc6b576c5aa13850551cc v2.5
> gpg: directory `/home/aubrey/.gnupg' created
> gpg: new configuration file `/home/aubrey/.gnupg/gpg.conf' created
> gpg: WARNING: options in `/home/aubrey/.gnupg/gpg.conf' are not yet
> active during this run
> gpg: keyring `/home/aubrey/.gnupg/secring.gpg' created
> gpg: keyring `/home/aubrey/.gnupg/pubring.gpg' created
> gpg: skipped "43368b967bd838292b8cc6b576c5aa13850551cc": secret key
> not available
> gpg: signing failed: secret key not available
> failed to sign the tag with GPG.
You seem to not have a working GnuPG installation, inclusing an
(already present) private key. Please first get familiar with GnuPG,
then try to use it :-) "gpg --gen-key" may help.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-03-02 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 15:51 Newbie question: git tag failure Aubrey
2006-03-02 15:54 ` Jan-Benedict Glaw [this message]
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=20060302155418.GZ19232@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=aubreylee@gmail.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