From: Leo Famulari <leo@famulari.name>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: Bad signature on commit 6a34f4ccc8a5d (gnu: python-prompt-toolkit: Update to 1.0.9.)
Date: Thu, 29 Dec 2016 01:39:35 -0500 [thread overview]
Message-ID: <20161229063935.GA26713@jasmine> (raw)
In-Reply-To: <20161229060818.GA29613@jocasta.intra>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
On Thu, Dec 29, 2016 at 07:08:18AM +0100, John Darrington wrote:
> On Thu, Dec 29, 2016 at 03:49:51AM +0100, Tobias Geerinckx-Rice wrote:
> Leo,
>
> On 29/12/16 03:10, Leo Famulari wrote:
> > gpg: BAD signature from "Tobias Geerinckx-Rice <me@tobias.gr>"
>
> Oh dear.
>
> > Does anyone else get the same result? Any ideas?
>
> I do, so it's a real?? corrupted signature.
>
> Looking back, it turns out that this isn't the first time this has
> happened: another commit of mine (7d162df, gnu: mcelog: Update to 146.)
> also has a bad signature, which I probably missed for the same reason.
>
>
> How did these commits get into the repository? Our repository is
> configured to reject unsigned commits. Can it be that it doesn't
> actually check that the signature matches? !!!
Yes, it's a known limitation:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22883#129
We need to improve the hook.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2016-12-29 6:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 2:10 Bad signature on commit 6a34f4ccc8a5d (gnu: python-prompt-toolkit: Update to 1.0.9.) Leo Famulari
2016-12-29 2:47 ` Leo Famulari
2016-12-29 3:04 ` Tobias Geerinckx-Rice
2016-12-29 17:13 ` Leo Famulari
2016-12-29 2:49 ` Tobias Geerinckx-Rice
2016-12-29 6:08 ` John Darrington
2016-12-29 6:39 ` Leo Famulari [this message]
2016-12-29 6:44 ` Leo Famulari
2016-12-29 7:38 ` Leo Famulari
2017-01-02 20:59 ` Ludovic Courtès
2017-01-03 6:24 ` Leo Famulari
2017-01-03 12:34 ` Ludovic Courtès
2017-01-03 17:29 ` Leo Famulari
2017-01-04 21:05 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161229063935.GA26713@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).