GNU bug report logs - #41767
[PATCH 0/9] Authenticate channels

Previous Next

Full log

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: zimoun <zimon.toutoune <at> gmail.com>
Cc: 41767 <at> debbugs.gnu.org
Subject: Re: [bug#41767] [PATCH 0/9] Authenticate channels
Date: Sun, 14 Jun 2020 15:51:36 +0200

Hi,

zimoun <zimon.toutoune <at> gmail.com> skribis:

>>> git clone https://git.savannah.gnu.org/git/guix.git
>>> git worktree add -b foo wk/foo
>>> cd wk/foo
>>> # add my unready stuff
>>> ./pre-inst-env guix pull --branch=foo --url=$PWS -p /tmp/foo
>>> /tmp/foo/bin/guix install unready-stuff
>>>
>>> In this case, do I have to use the option '--disable-authentication'?
>>
>> Yes, you can always use it.
>
> "Qui peut le plus peut le moins." ;-)
>
> The question is: is it mandatory?

If you have a local fork with unauthorized commits (for instance, you
made commits yourself and you’re not listed in ‘.guix-authorizations’)
then yes, you have to use ‘--disable-authentication’.

The alternative for you would be to publish an introduction for your
fork, which means you would be able to test which is the first commit to
authenticate.

However, this may be inconvenient for one-off forks where you just want
to test changes.  In that case, ./pre-inst-env probably remains the
preferred approach.

Thanks,
Ludo’.

Previous Next

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