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 04:04:49 +0100 [thread overview]
Message-ID: <20387f2e-ea7d-fb62-5b2f-09ec3e0a37f2@tobias.gr> (raw)
In-Reply-To: <20161229024733.GA9193@jasmine>
[-- Attachment #1.1: Type: text/plain, Size: 779 bytes --]
Leo,
On 29/12/16 03:47, Leo Famulari wrote:
> I'm also unable to verify the signature of two more commits, as below.
Signing seems to fail both seldom and pseudo-randomly. Oh, and
silently[1]. My favourite kind of bug.
I'm guessing this is what happens:
$
$ git commit, am or cherry-pick && git log --show-signatures
...everything looks good and signed! Let's push!
$ git fetch --all && git rebase upstream/master
...now signing some non-HEAD commit silently fails...
$ git push upstream
...badness.
Good night,
T G-R
[1]: until you check the log, of course.
PS:
nckx@ubuntu~$ $ /usr/bin/gpg2 --version
gpg (GnuPG) 2.1.15
libgcrypt 1.7.2-beta
but I doubt that matters much now. I don't use Guix's gpg [yet].
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 476 bytes --]
next prev parent reply other threads:[~2016-12-29 3:04 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 [this message]
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=20387f2e-ea7d-fb62-5b2f-09ec3e0a37f2@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 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.