From: Fulbert <fulbert@bluewin.ch>
To: help-guix@gnu.org
Subject: Re: error: corrupt input while restoring archive from socket
Date: Tue, 9 Mar 2021 10:19:28 +0100 [thread overview]
Message-ID: <YEc9oFsimJgxT1WH@bluewin.ch> (raw)
In-Reply-To: <2b46f49ff5d1dbe7e56dcce44abd23c478cf0ce0.camel@divoplade.fr>
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
> > issues.guix.gnu.org.
> 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.
next prev parent reply other threads:[~2021-03-09 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 7:48 error: corrupt input while restoring archive from socket Fulbert
2021-03-09 7:52 ` divoplade
2021-03-09 9:19 ` Fulbert [this message]
2021-03-11 13:59 ` Mikhail Kryshen
2021-03-11 14:41 ` Fulbert
2021-03-11 17:59 ` Mikhail Kryshen
2021-03-16 18:16 ` Bonface Munyoki K.
2021-03-12 0:08 ` Mikhail Kryshen
2021-03-12 14:56 ` Mikhail Kryshen
2021-03-22 10:17 ` Fulbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YEc9oFsimJgxT1WH@bluewin.ch \
--to=fulbert@bluewin.ch \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.