unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: divoplade <d@divoplade.fr>
To: Fulbert <fulbert@bluewin.ch>, help-guix@gnu.org
Subject: Re: error: corrupt input while restoring archive from socket
Date: Tue, 09 Mar 2021 08:52:12 +0100	[thread overview]
Message-ID: <2b46f49ff5d1dbe7e56dcce44abd23c478cf0ce0.camel@divoplade.fr> (raw)
In-Reply-To: <YEcoSSVQQ0zxXAzh@bluewin.ch>

Hello,

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.
> 
> 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.



  reply	other threads:[~2021-03-09  7:53 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 [this message]
2021-03-09  9:19   ` Fulbert
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2b46f49ff5d1dbe7e56dcce44abd23c478cf0ce0.camel@divoplade.fr \
    --to=d@divoplade.fr \
    --cc=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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).