git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Carlos Rica" <jasampler@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: skimo@liacs.nl, git@vger.kernel.org
Subject: Re: t7004-tag.sh fails (old gpg?)
Date: Sun, 1 Jul 2007 17:45:37 +0200	[thread overview]
Message-ID: <1b46aba20707010845s69fd3915p8460392ad92bba4b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707011507310.4438@racer.site>

2007/7/1, Johannes Schindelin <Johannes.Schindelin@gmx.de>:
> On Sun, 1 Jul 2007, Sven Verdoolaege wrote:
>
> > 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
>
> That means that gpg somehow barfs on the keyring. I somehow had the
> impression that the keyrings were binary compatible on different
> systems... What system do you have?
>
> > bash-3.00$ gpg --version
> > gpg (GnuPG) 1.0.6
>
> It is 1.4.5 here.

I have gpg (GnuPG) 1.4.1 here, in the system I used to generate the key.

      parent reply	other threads:[~2007-07-01 15:45 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
2007-07-01 15:45   ` Carlos Rica [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=1b46aba20707010845s69fd3915p8460392ad92bba4b@mail.gmail.com \
    --to=jasampler@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --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).