GNU bug report logs - #42604
Manual section on building Guix from Git is incomplete

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 42604 in the body.
You can then email your comments to 42604 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: Tirifto <tirifto <at> posteo.cz>
To: bug-guix <at> gnu.org
Subject: Manual section on building Guix from Git is incomplete
Date: Wed, 29 Jul 2020 15:03:46 +0000

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

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

From: zimoun <zimon.toutoune <at> gmail.com>
To: Tirifto <tirifto <at> posteo.cz>
Cc: 42604 <at> debbugs.gnu.org
Subject: Re: bug#42604: Manual section on building Guix from Git is incomplete
Date: Mon, 05 Jul 2021 11:44:39 +0200

Hi,

Thanks for the report.

On Wed, 29 Jul 2020 at 15:03, Tirifto <tirifto <at> 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

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

From: zimoun <zimon.toutoune <at> gmail.com>
To: Tirifto <tirifto <at> posteo.cz>
Cc: 42604-done <at> debbugs.gnu.org
Subject: Re: bug#42604: Manual section on building Guix from Git is incomplete
Date: Tue, 17 Aug 2021 23:33:41 +0200

Hi,

On Mon, 05 Jul 2021 at 11:44, zimoun <zimon.toutoune <at> gmail.com> wrote:
> On Wed, 29 Jul 2020 at 15:03, Tirifto <tirifto <at> 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>

I am closing.  If I miss something, feel free to reopen.


All the best,
simon

Previous Next

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