unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: Guix publish pipe error from #{read pipe}#
Date: Tue, 16 May 2017 08:57:13 +0200	[thread overview]
Message-ID: <877f1hffw6.fsf@igalia.com> (raw)
In-Reply-To: <20170516062917.GA7072@thebird.nl> (Pjotr Prins's message of "Tue, 16 May 2017 08:29:17 +0200")

On Tue 16 May 2017 08:29, Pjotr Prins <pjotr.public12@thebird.nl> writes:

> On a recent guix-publish server I get many of these
>
>   gzip: stdin: invalid compressed data--format violated
>     r-annotationdbi-1.36.0
>     1.7MiB/s 00:02 | 3.0MiB transferredguix substitute: error: corrupt
>   input while restoring
>     '/gnu/store/g33ns71m61zs5sn758smmc4lnv6h4c4q-r-annotationdbi-1.36.0/site-library/AnnotationDbi/extdata/HG-U95Av2_probe_tab.gz' from #{read pipe}#
>
> I don't think this is a guix problem per se. I have a hunch the people
> changed the firewall which may cause this.  Anyone any other ideas?

IME this means that the .nar or whatever was truncated by some
intermediate cache.  Like if you wget the file and try to gunzip it, it
will give the same error AFAIU.

Andy

  reply	other threads:[~2017-05-16  6:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16  6:29 Guix publish pipe error from #{read pipe}# Pjotr Prins
2017-05-16  6:57 ` Andy Wingo [this message]
2017-05-17  7:10 ` Guix publish pipe error from #{read pipe}# - what nginx.conf to use? Pjotr Prins
2017-05-17 12:48   ` Ludovic Courtès

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=877f1hffw6.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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