From: Tirifto <tirifto@posteo.cz>
To: 42604@debbugs.gnu.org
Subject: bug#42604: Manual section on building Guix from Git is incomplete
Date: Wed, 29 Jul 2020 15:03:46 +0000 [thread overview]
Message-ID: <20200729150346.43ab4681@posteo.cz> (raw)
Hello!
The manual describes how to fetch Guix from Git in section ‘14.1
Building from Git’, including how to verify the authenticity of the
copy. Quoting the part in question:
> If you want to hack Guix itself, it is recommended to use the latest
> version from the Git repository:
>
> git clone https://git.savannah.gnu.org/git/guix.git
>
> How do you ensure that you obtained a genuine copy of the
> repository? To do that, run ‘guix git authenticate’, passing if the
> commit and OpenPGP fingerprint of the “channel introduction” (*note
> Invoking guix git authenticate::):
>
> guix git authenticate 9edb3f66fd807b096b48283debdcddccfea34bad \
> "BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA"
>
> This command completes with exit code zero on success; it prints an
> error message and exits with a non-zero code otherwise.
I have encountered two problems here:
1.‘guix git authenticate’ only works after the branch ‘keyring’ has
been set up locally; I’ve been told to achieve this with the
command ‘git fetch upstream keyring:keyring’, but ‘git checkout
keyring’ has worked for me, too. After that, it seems to be
necessary to switch back to the master branch to successfully run
‘guix git authenticate’. I think the commands for this should be
included in this section.
2. The word ‘if’ seems to be a typo of ‘it’. I first thought that the
sentence was incomplete and that the command should pass if the
commit and the fingerprint [did something]. :)
Not sure how the first one would be solved the best.
Best of wishes
// Tirifto
next reply other threads:[~2020-07-29 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 15:03 Tirifto [this message]
2021-07-05 9:44 ` bug#42604: Manual section on building Guix from Git is incomplete zimoun
2021-08-17 21:33 ` zimoun
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=20200729150346.43ab4681@posteo.cz \
--to=tirifto@posteo.cz \
--cc=42604@debbugs.gnu.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.
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).