From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 51822@debbugs.gnu.org
Subject: [bug#51822] [PATCH] gnupg: Honor GnuPG's configuration for the key server.
Date: Thu, 18 Nov 2021 10:57:05 -0500 [thread overview]
Message-ID: <87pmqxfodq.fsf@gmail.com> (raw)
In-Reply-To: <CAJ3okZ2CT+ozXHzoz2MEcf+=1qUCNs0n_AiYXLv_fi1bWBwLbg@mail.gmail.com> (zimoun's message of "Thu, 18 Nov 2021 15:29:29 +0100")
Hi,
zimoun <zimon.toutoune@gmail.com> writes:
> Re,
>
> On Thu, 18 Nov 2021 at 15:21, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>
>> > If a server was used for doing something by Guix at version A, then
>> > this server is now down, is the something still now doable using this
>> > old version A of Guix? Where this old version A is reachable by "guix
>> > time-machine".
>> >
>> > Maybe it does not make sense and it is not relevant.
>>
>> The default server that was hard-coded in Guix (or in GnuPG) in the past
>> would still not work *now*, even using an older Guix commit :-).
>
> Yeah, for sure. My question is: because this server is not working
> *now* and hard-coded on previous version, is "guix time-machine" still
> working for all the subcommands? Or is it broken as collateral damage
> of server down + hard coded? :-)
guix time-machine is not broken as a whole, but the 'guix refresh
--update' commands that makes use of the (guix gnupg) module would for
sure in whichever commit of Guix, unless pool.sks-keyservers.net is
revived. As a workaround, the --key-server option can be set to
hkp://keyserver.ubuntu.com (what became the default in recent GnuPG
releases).
Thanks,
Maxim
next prev parent reply other threads:[~2021-11-18 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 2:51 [bug#51822] [PATCH] gnupg: Honor GnuPG's configuration for the key server Maxim Cournoyer
2021-11-15 10:31 ` zimoun
2021-11-18 13:01 ` Maxim Cournoyer
2021-11-18 13:35 ` zimoun
2021-11-18 14:21 ` Maxim Cournoyer
2021-11-18 14:29 ` zimoun
2021-11-18 15:57 ` Maxim Cournoyer [this message]
2021-11-18 16:20 ` zimoun
2021-11-18 20:05 ` bug#51822: " Maxim Cournoyer
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=87pmqxfodq.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=51822@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).