From: Sven Verdoolaege <skimo@kotnet.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Carlos Rica <jasampler@gmail.com>, git@vger.kernel.org
Subject: Re: t7004-tag.sh fails (old gpg?)
Date: Sun, 01 Jul 2007 21:10:18 +0200 [thread overview]
Message-ID: <20070701191018.GM7969MdfPADPa@greensroom.kotnet.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707011929200.4438@racer.site>
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
On Sun, Jul 01, 2007 at 07:30:09PM +0100, Johannes Schindelin wrote:
> Aargh! I am a complete moron. Attached also the private key now.
Ok... some progress...
* expecting success: git-tag -v signed-tag
object 86e17e4ed4cddf9a4f960da789f8378f6ea1ff2b
type commit
tag signed-tag
tagger C O Mitter <committer@example.com> Thu Apr 7 15:13:13 2005 -0700
A signed tag message
gpg: Warning: using insecure memory!
gpg: Signature made Sun Jul 1 19:08:37 2007 UTC using DSA key ID CDDE430D
gpg: Good signature from "C O Mitter <committer@example.com>"
gpg: NOTE: secret key CDDE430D is NOT protected.
gpg: /home/skimo/src/git/t/trash/gpghome/trustdb.gpg: invalid file version 3
gpg: fatal: /home/skimo/src/git/t/trash/gpghome/trustdb.gpg: invalid trustdb
secmem usage: 1408/1408 bytes in 2/2 blocks of pool 1408/16384
* FAIL 50: verifying a signed tag should succeed
git-tag -v signed-tag
skimo
[-- Attachment #2: secring.gpg --]
[-- Type: application/octet-stream, Size: 1229 bytes --]
next prev parent reply other threads:[~2007-07-01 19:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 12:49 t7004-tag.sh fails (old gpg?) Sven Verdoolaege
2007-07-01 14:09 ` 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 [this message]
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=20070701191018.GM7969MdfPADPa@greensroom.kotnet.org \
--to=skimo@kotnet.org \
--cc=Johannes.Schindelin@gmx.de \
--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).