From: Sven Verdoolaege <skimo@kotnet.org>
To: Carlos Rica <jasampler@gmail.com>
Cc: git@vger.kernel.org
Subject: t7004-tag.sh fails (old gpg?)
Date: Sun, 01 Jul 2007 14:49:53 +0200 [thread overview]
Message-ID: <20070701124953.GH7969MdfPADPa@greensroom.kotnet.org> (raw)
t7004-tag.sh fails for me:
* expecting success:
git-tag -s -m "A signed tag message" signed-tag &&
get_tag_msg signed-tag >actual &&
git-diff expect actual
gpg: Warning: using insecure memory!
gpg: [don't know]: invalid packet (ctb=00)
gpg: read_keyblock: read error: invalid packet
gpg: enum_keyblocks failed: invalid keyring
gpg: skipped `C O Mitter <committer@example.com>': invalid keyring
gpg: signing failed: invalid keyring
failed to sign the tag with GPG.
* FAIL 49: creating a signed tag with -m message should succeed
git-tag -s -m "A signed tag message" signed-tag &&
get_tag_msg signed-tag >actual &&
git-diff expect actual
I see that you alread check for presence of gpg, but maybe
you should also check that it is recent enough.
This is the version I have:
bash-3.00$ gpg --version
gpg (GnuPG) 1.0.6
Copyright (C) 2001 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.
Home: ~/.gnupg
Supported algorithms:
Cipher: 3DES, CAST5, BLOWFISH, RIJNDAEL, RIJNDAEL192, RIJNDAEL256, TWOFISH
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA, ELG
Hash: MD5, SHA1, RIPEMD160
skimo
next reply other threads:[~2007-07-01 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 12:49 Sven Verdoolaege [this message]
2007-07-01 14:09 ` t7004-tag.sh fails (old gpg?) Johannes Schindelin
2007-07-01 15:34 ` Sven Verdoolaege
2007-07-01 16:06 ` Carlos Rica
2007-07-01 16:53 ` Sven Verdoolaege
2007-07-01 18:06 ` Johannes Schindelin
2007-07-01 18:26 ` Sven Verdoolaege
2007-07-01 18:30 ` Johannes Schindelin
2007-07-01 19:10 ` Sven Verdoolaege
2007-07-01 15:45 ` Carlos Rica
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=20070701124953.GH7969MdfPADPa@greensroom.kotnet.org \
--to=skimo@kotnet.org \
--cc=git@vger.kernel.org \
--cc=jasampler@gmail.com \
--cc=skimo@liacs.nl \
/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).