unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: leo@famulari.name, 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 03:49:51 +0100	[thread overview]
Message-ID: <3cd2cda0-e1c7-9b6d-b04c-b31302a0fe45@tobias.gr> (raw)
In-Reply-To: <20161229021015.GA16162@jasmine>


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

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.

Kind regards,

T G-R


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 476 bytes --]

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

  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=3cd2cda0-e1c7-9b6d-b04c-b31302a0fe45@tobias.gr \
    --to=me@tobias.gr \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).