GNU bug report logs - #40276
[PATCH] doc: Update instructions to bootstrap the trust chain.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 40276 in the body.
You can then email your comments to 40276 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jacob First <jacob.k.first <at> gmail.com>
Subject: [PATCH] doc: Update instructions to bootstrap the trust chain.
Date: Sun, 29 Mar 2020 08:21:22 -0400

* doc/contributing.texi (Building from Git): Clarify that multiple committers'
keys may now be used to sign changes to git-authenticate.scm. For context see
<https://lists.gnu.org/archive/html/guix-devel/2020-03/msg00433.html>.
---
 doc/contributing.texi | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index 31b875f817..ed6c952ba0 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -64,8 +64,14 @@ gpg:                using RSA key 3CE464558A84FDC69DB40CFB090B11993D9AEBB5
 
 @noindent
 ... meaning that changes to this file are all signed with key
-@code{3CE464558A84FDC69DB40CFB090B11993D9AEBB5} (you may need to fetch
-this key from a key server, if you have not done it yet).
+@code{3CE464558A84FDC69DB40CFB090B11993D9AEBB5}. You may see other keys as well,
+as other contributors and/or maintainers may also commit to this
+file <at> footnote{For context about this change, see
+@url{https://lists.gnu.org/archive/html/guix-devel/2020-03/msg00433.html,
+this explanation} on the guix-devel mailing list.}. If you are missing any keys,
+fetch them from the respective committers'
+@url{https://savannah.gnu.org/project/memberlist.php?group=guix, Savannah
+profiles} and re-run the verification.
 
 From there on, you can authenticate all the commits included in your
 checkout by running:
-- 
2.26.0

Message #10 received at 40276 <at> debbugs.gnu.org (full text, mbox):

From: Jacob First <jacob.k.first <at> gmail.com>
To: 40276 <at> debbugs.gnu.org
Subject: Re: [PATCH] doc: Update instructions to bootstrap the trust chain.
Date: Fri, 16 Oct 2020 06:42:10 +0000

[Message part 1 (text/plain, inline)]

I'm pretty sure this can be closed. As of 63c799c1 the instructions were
changed to use `guix git authenticate` so the additional advice is no
longer relevant.

[Message part 2 (text/html, inline)]

Message #13 received at 40276 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Jacob First <jacob.k.first <at> gmail.com>
Cc: 40276 <at> debbugs.gnu.org
Subject: Re: [bug#40276] [PATCH] doc: Update instructions to bootstrap the
 trust chain.
Date: Fri, 16 Oct 2020 13:23:57 +0200

Dear,

Thank you for you patch.

On Fri, 16 Oct 2020 at 06:42, Jacob First <jacob.k.first <at> gmail.com> wrote:

> I'm pretty sure this can be closed. As of 63c799c1 the instructions
> were changed to use `guix git authenticate` so the additional advice
> is no longer relevant.

Indeed.

Since you submitted the patch, feel free to close it. :-)  To do so, you
simply answer to 40276-done <at> debbugs.gnu.org with the explanation why the
report is closed (as you did).


Thanks,
simon

Message #18 received at 40276-done <at> debbugs.gnu.org (full text, mbox):

From: Jacob First <jacob.k.first <at> gmail.com>
To: 40276-done <at> debbugs.gnu.org
Subject: Re: [PATCH] doc: Update instructions to bootstrap the trust chain.
Date: Fri, 16 Oct 2020 11:32:48 +0000

[Message part 1 (text/plain, inline)]

Closing this. As of 63c799c1 the instructions were changed to use `guix git
authenticate` so the additional advice is no longer relevant.

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.