unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Tirifto <tirifto@posteo.cz>
Cc: 42604@debbugs.gnu.org
Subject: bug#42604: Manual section on building Guix from Git is incomplete
Date: Mon, 05 Jul 2021 11:44:39 +0200	[thread overview]
Message-ID: <87a6n1ksc8.fsf@gmail.com> (raw)
In-Reply-To: <20200729150346.43ab4681@posteo.cz> (tirifto@posteo.cz's message of "Wed, 29 Jul 2020 15:03:46 +0000")

Hi,

Thanks for the report.

On Wed, 29 Jul 2020 at 15:03, Tirifto <tirifto@posteo.cz> wrote:

> 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.

I think the latest [1] version of the manual fixes the 2 issue.  WDYT?

1: <http://guix.gnu.org/manual/devel/en/guix.html#Building-from-Git>

All the best,
simon




  reply	other threads:[~2021-07-05 10:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 15:03 bug#42604: Manual section on building Guix from Git is incomplete Tirifto
2021-07-05  9:44 ` zimoun [this message]
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=87a6n1ksc8.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=42604@debbugs.gnu.org \
    --cc=tirifto@posteo.cz \
    /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).