[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: error: corrupt input while restoring archive from socket

From: Fulbert
Subject: Re: error: corrupt input while restoring archive from socket
Date: Tue, 9 Mar 2021 10:19:28 +0100

Le Tue, Mar 09, 2021 at 08:52:12AM +0100, divoplade a écrit :
> Hello,

Hello Divoplade and thanks for your help,

> Le mardi 09 mars 2021 à 08:48 +0100, Fulbert a écrit :
> > 
> > Attached, 2 files with such an error. Note that I have
> > translated the messages back to english (from french)… just in
> > case you find some typos and wonder how guix could mistype… ^^
> You can run LANG=C guix ... to directly have the error messages in
> english.

Good tip. I knew and used it but, as I said, it is not reproducible
so I would have to setup english as main language to catch all
errors in english… and would miss bugs limited/related to french
translations ;]

> > 
> > The error message common to all those recent failures is :
> >   error: corrupt input while restoring archive from socket
> > 
> > Any idea ? I have not found any recent similar issue on
> >
> I have had similar problems, you might want to run with --fallback (for
> guix pull, guix package) to compile from source if the substitutes are
> buggy.

Good tip again and will use it when stuck on one substitute. Thank
you.  It's just that here, the problem does not realy seem to be
buggy substitutes, as subsequent attempts would [generally] succeed. 

And if the transmissions over the network were to blame, I guess I
would have other issues besides guix substitutes ?! So… I am curious
as to what could cause this recent rise in guix substitue errors,
and eventually, how to fix it.

Thanks again for your time and help.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]