GNU bug report logs - #57559
guix pull fails on http status code 503

Previous Next

Full log

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

From: zimoun <zimon.toutoune <at> gmail.com>
To: Maxime Devos <maximedevos <at> telenet.be>, André A. Gomes
 <andremegafone <at> gmail.com>, 57559 <at> debbugs.gnu.org
Subject: Re: bug#57559: guix pull fails on http status code 503
Date: Thu, 08 Sep 2022 09:25:29 +0200

Hi Maxime,

On Thu, 08 Sep 2022 at 02:55, Maxime Devos <maximedevos <at> telenet.be> wrote:

>> Well, %default-guix-channel is somehow a corner use-case when the
>> regular use-case seems about a failure of additional channels.
>
> The ‘Guix is unavailable’ was just a simple example. For the example, 
> you can replace it, with, say nonguix. Automatically removing the 
> additional channels upon 503 is undesirable I'd think, though the error 
> messages will be different.

My point is that ’Guix is unavailable’ is special and it appears to me
expected to raise an error.  Other said,

 1. if %default-guix-channel (or its mirrors) is unreachable,
    then stop the pull; as it is currently done.
 2. if an extra channel is unreachable,
    then keep the last local revision of this channel
    and try the others.

For sure, #2 can break the whole pull if something in the Guix channel
changed *and* the channel depends on this something.  But we cannot do
more than raise an error.


Cheers,
simon

Previous Next

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