all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 03/03: doc: Update to cover for an additional OpenPGP signing key.
Date: Tue, 04 May 2021 17:29:07 +0200	[thread overview]
Message-ID: <87y2cuplfg.fsf@gnu.org> (raw)
In-Reply-To: <874kfin16n.fsf@gmail.com> (Maxim Cournoyer's message of "Tue, 04 May 2021 08:17:04 -0400")

Hello!

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> Oh, it didn't strike me as an option, as it'd not cover past releases.
> Perhaps not a common use case, but the past releases are still available
> for download, so someone could want to install them, perhaps just to
> compare what changed or decide if some problem is regression.

IMO that’s OK, that’s the same as with other releases at ftp.gnu.org.
It’s the user’s responsibility to fetch the right key.

I think it’s enough for the instructions in the manual to apply only to
the latest release.  So I’d suggest reverting and setting
OPENPGP-SIGNING-KEY-ID and OPENPGP-SIGNING-KEY-URL to your key.

WDYT?

(Conversely, it’s good for guix-install.sh to suggest both keys since it
can be used to install both 1.2.0 and 1.3.0rc1 right now.)

Thanks,
Ludo’.


  reply	other threads:[~2021-05-04 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210504033511.24042.17383@vcs0.savannah.gnu.org>
     [not found] ` <20210504033513.A0CFA20D0E@vcs0.savannah.gnu.org>
2021-05-04  9:08   ` 03/03: doc: Update to cover for an additional OpenPGP signing key Ludovic Courtès
2021-05-04 10:57     ` Julien Lepiller
2021-05-04 12:17       ` Maxim Cournoyer
2021-05-04 15:29         ` Ludovic Courtès [this message]
2021-05-05 15:39           ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y2cuplfg.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@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 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.