From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GPG key refresh
Date: Tue, 15 Dec 2020 10:44:02 -0500 [thread overview]
Message-ID: <06fc8db4-8785-44ab-2a03-8dce505c1b55@gentoo.org> (raw)
In-Reply-To: <001101d6d2f6$cf6bbae0$6e4330a0$@gentoo.org>
On 12/15/20 10:27 AM, Thomas Deutschmann wrote:
> Hi,
>
> what exactly did you do already?
>
> Did you uploaded to our internal key server? You can only upload
> through dev.gentoo.org, see
> https://wiki.gentoo.org/wiki/Project:Infrastructure/Generating_GLEP_63_based_OpenPGP_keys#Submit_your_new_key_to_the_keyserver
>
> However, you can pull from this server.
>
> I tried to test your key but I am currently getting a failure from
> our keyserver. Waiting for infra to check.
>
It's working now. I hadn't pushed directly to the internal server,
unaware that it was still internal. An update to the error message (git
hook) that mentions that wiki page could mitigate similar headaches in
the future. GLEP63 still says,
== Bare minimum requirements ==
...
7. Upload your key to the SKS keyserver rotation before usage!
which should also be amended if there's no imminent plan to resume
pulling keys from there.
next prev parent reply other threads:[~2020-12-15 15:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 18:59 [gentoo-dev] GPG key refresh Michael Orlitzky
2020-12-14 19:17 ` Alec Warner
2020-12-14 19:41 ` Michael Orlitzky
2020-12-15 15:27 ` Thomas Deutschmann
2020-12-15 15:44 ` Michael Orlitzky [this message]
2020-12-15 15:49 ` Michael Orlitzky
2020-12-15 16:11 ` Thomas Deutschmann
2020-12-15 16:16 ` Michael Orlitzky
2020-12-16 4:37 ` Aaron W. Swenson
2020-12-16 8:01 ` Michał Górny
2020-12-17 4:48 ` desultory
2020-12-17 18:28 ` Mike Gilbert
2020-12-17 19:23 ` Michał Górny
2020-12-17 18:35 ` Mike Gilbert
2020-12-17 19:22 ` Michał Górny
2020-12-14 19:24 ` Cédric Krier
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=06fc8db4-8785-44ab-2a03-8dce505c1b55@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox