all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: Bad signature on commit 6a34f4ccc8a5d (gnu: python-prompt-toolkit: Update to 1.0.9.)
Date: Wed, 28 Dec 2016 21:47:33 -0500	[thread overview]
Message-ID: <20161229024733.GA9193@jasmine> (raw)
In-Reply-To: <20161229021015.GA16162@jasmine>


[-- Attachment #1.1: Type: text/plain, Size: 1996 bytes --]

On Wed, Dec 28, 2016 at 09:10:15PM -0500, Leo Famulari wrote:
> I see this in the log:
> 
> $ git log --show-signature 6a34f4ccc8a5d4a48e25ad3c9c512f8634928b91
> commit 6a34f4ccc8a5d4a48e25ad3c9c512f8634928b91
> gpg: Signature made Wed 28 Dec 2016 08:38:21 PM EST
> gpg:                using RSA key 91CCDB9B48541B99
> gpg: BAD signature from "Tobias Geerinckx-Rice <me@tobias.gr>" [unknown]
> Author: Tobias Geerinckx-Rice <me@tobias.gr>
> Date:   Wed Dec 28 23:01:49 2016 +0100
> 
>     gnu: python-prompt-toolkit: Update to 1.0.9.
>     
>     * gnu/packages/python.scm (python-prompt-toolkit): Update to 1.0.9.
> 
> Does anyone else get the same result? Any ideas?
> 
> Tobias, what version of GnuPG are you using?
> 
> I'm using:
> 
> gnupg	2.1.17	/gnu/store/1sa7k3x3y3chdl31p7y7x3sa7p9h1qa3-gnupg-2.1.17
> 
> ... which is built from Guix commit 791ac6a68d1e4bc80f4760cd968cb6c26dbab9ba.

I'm also unable to verify the signature of two more commits, as below.
I've attached a handy Git signature verifier script.

commit e0f8a520eda6b86a71f99eddf2c6968a95c8de0e
gpg: Signature made Thu 24 Nov 2016 08:21:51 PM EST
gpg:                using RSA key 91CCDB9B48541B99
gpg: BAD signature from "Tobias Geerinckx-Rice <me@tobias.gr>" [unknown]
Author: Tobias Geerinckx-Rice <me@tobias.gr>
Date:   Thu Nov 24 19:28:52 2016 +0100

    gnu: miniupnpc: Improve synopsis and description.
    
    * gnu/packages/upnp.scm (miniupnp)[synopsis, description]: Edit, fix typos,
    add some relevant (search) terms from the home page, and expand acronyms.

commit 7d162df8ce4dc90c681ff627b2ed94c192e6342f
gpg: Signature made Thu 15 Dec 2016 09:08:42 PM EST
gpg:                using RSA key 91CCDB9B48541B99
gpg: BAD signature from "Tobias Geerinckx-Rice <me@tobias.gr>" [unknown]
Author: Tobias Geerinckx-Rice <me@tobias.gr>
Date:   Thu Dec 15 23:17:52 2016 +0100

    gnu: mcelog: Update to 146.
    
    * gnu/packages/linux.scm (mcelog): Update to 146.

[-- Attachment #1.2: verifier --]
[-- Type: text/plain, Size: 606 bytes --]

#!/bin/sh

# This script requires a Git revision selector, such as HEAD, 734713bc0,
# origin/master..HEAD, et cetera:
# https://git-scm.com/book/en/v2/Git-Tools-Revision-Selection

# A revision selector example for guix.git: v0.11.0..HEAD

if test $# -eq 1 ; then
	range=$1
else
	exit 1
fi

for commit in $(git rev-list $range); do
	results=$(git verify-commit $commit 2>&1)
	if test $? -ne 0; then
		git show --format=full --show-signature $commit
		# I'm not sure if the previous line will always include the
		# contents of $results, so I re-print it just in case.
		printf "%s\n\n" "$results"
	fi
done

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2016-12-29  2:47 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161229024733.GA9193@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.