From: Eric Bavier <bavier@posteo.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 40565@debbugs.gnu.org
Subject: bug#40565: make authenticate fails: commit 77704cb13e5bebf412297dab764a00849a3cfdc0: key A0C5E3522EF8EF5C64CDB7F0FD73CAC719D32566 is missing
Date: Thu, 16 Apr 2020 20:52:48 -0500 [thread overview]
Message-ID: <6a77de5459916e45838f18afce850b8f@posteo.net> (raw)
In-Reply-To: <87r1wnz9g7.fsf@nckx>
On 16.04.2020 11:24, Tobias Geerinckx-Rice wrote:
> Ela, Eric,
>
> elaexuotee--- via Bug reports for GNU Guix 写道：
>> It looks like the referenced key doesn't exist in the keyservers:
>>
>> $ gpg --recv-keys A0C5E3522EF8EF5C64CDB7F0FD73CAC719D325
>> gpg: keyserver receive failed: No data
>>
> Eric, I didn't find any previous discussion about this. Could you
> help us out by publishing this ‘secret’ key somewhere? :-)
>
> Your key at Savannah[0] is a different one and there's no
> A0C5E3522EF8EF5C64CDB7F0FD73CAC719D325 on keys.openpgp.org, SKS,
> keys.gnupg.net, or pgp.mit.edu.
A0C5E352... is a signing subkey. The key on Savannah, 34FF38BC..., is
the primary key. The signature checks out with my primary key.
--
`~Eric
next prev parent reply other threads:[~2020-04-17 1:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 2:55 bug#40565: make authenticate fails: commit 77704cb13e5bebf412297dab764a00849a3cfdc0: key A0C5E3522EF8EF5C64CDB7F0FD73CAC719D32566 is missing elaexuotee--- via Bug reports for GNU Guix
2020-04-16 16:24 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-04-17 1:52 ` Eric Bavier [this message]
2020-04-17 11:15 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-04-17 17:39 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-04-17 20:20 ` bug#40565: [PATCH 0/1] bug#40565: make authenticate fails Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-04-17 20:20 ` bug#40565: [PATCH 1/1] git-authenticate: Fetch keyrings from Savannah Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-04-19 11:15 ` Ludovic Courtès
2020-05-04 9:02 ` 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=6a77de5459916e45838f18afce850b8f@posteo.net \
--to=bavier@posteo.net \
--cc=40565@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.