GNU bug report logs - #41908
guix time-machine fails; XXXX is not related to introductory commit of channel 'guix'

Previous Next

Full log

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: zimoun <zimon.toutoune <at> gmail.com>
Cc: 41908-done <at> debbugs.gnu.org, Jan Nieuwenhuizen <janneke <at> gnu.org>
Subject: Re: bug#41908: guix time-machine fails;
 XXXX is not related to introductory commit of channel 'guix'
Date: Tue, 23 Jun 2020 10:53:46 +0200

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

> Just to be sure to understand:
>
>  1- * 41a2d6a8b9 (newer)
>  2- * e70e097882 (between)
>  3- * 36640207c9 (older)
>  4- * xxxxxxxxxx (first authenticated commit)
>
> From a fresh cache,
>
>  a) if #2 is authenticated, because it is descendant of #4, it is stored
>  and all the commits between (closure), i.e., #3 should be considered as
>  authenticated.
>
>  b) then if #1 is authenticated, because it is a descendant of the last
>  authenticated i.e. #2, it is stored in the cache.
>
>  c) now let try #3.  It is considered authenticated because in the closure
>  of #4 and #2.
>
> Yes it makes sense.  All is good. :-)

Yup, looks correct.  :-)

> (And the assumption is: if Guix does not raise then it means that the
> commit is authenticated.)

Exactly.  I know it’s disappointing, but it’s one of these features
that’s pretty much invisible until you run into troubles.

Ludo’.

Previous Next

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