[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#42048] [PATCH 6/6] services: provenance: Save channel introductions
[bug#42048] [PATCH 6/6] services: provenance: Save channel introductions.
Wed, 01 Jul 2020 19:05:17 +0200
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
zimoun <firstname.lastname@example.org> skribis:
> On Wed, 01 Jul 2020 at 14:12, Ludovic Courtès <email@example.com> wrote:
>> I’m talking about the warning that says “this channel is
>> unauthenticated”, which is mostly orthogonal to the discussion at hand.
>> The reason I said it’s perhaps too early to enable it is that people
>> haven’t had a chance to make their channel “authenticable” yet.
To be clear, I’m referring to this:
> Well, the possible scenarii are: when pulling guix-bimsb which ends up
> to pull guix-past:
> 1- unauthenticated guix-bimsb and unauthenticated guix-past
> 2- authenticated guix-bimsb and unauthenticated guix-past
> 3- unauthenticated guix-bimsb and authenticated guix-past
> 4- authenticated guix-bimsb and authenticated guix-past
> The #1 and #4 do not deserve a warning.
> The point #3 neither and even the authentication of guix-past should be
> turned off, at least now.
> The point #2 requires a warning. Because if I am pulling a
> authenticated channel, I expect that all the code it pulls is
> authenticated which will not be the case, so IMHO it deserves a
> Then it is up to the guix-bimsb channel to add an introduction for the
> dependency using the format you described.
Exactly. I agree that #2 is problematic, but if the authors of
guix-bimsb are aware that guix-past can also be authenticated, then I
think it’s their responsibility to update their ‘.guix-channel’