From: Christopher Allan Webber <cwebber@dustycloud.org>
To: 23103@debbugs.gnu.org
Subject: bug#23103: A number of corrupt packages on Hydra?
Date: Wed, 23 Mar 2016 16:48:50 -0700 [thread overview]
Message-ID: <87h9fwiwm5.fsf@dustycloud.org> (raw)
For at least boost and hydra I'm getting errors like the following:
From http://hydra.gnunet.org/nar/jaf2s3paa3fswfpzi6amlqjxd3fwiw9x-ruby-2.3.0
Downloading jaf2s3...-ruby-2.3.0 (41.9MiB installed)...
http://hydra.gnunet.org/nar/jaf2s3paa3fswfpzi6amlqjxd3fwiw9x-ruby-2.3.0 2.0MiB/s 00:02 | 3.4MiB transferredd
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
guix substitute: error: corrupt input while restoring '/gnu/store/jaf2s3paa3fswfpzi6amlqjxd3fwiw9x-ruby-2.3.0/lib/ruby/2.3.0/rdoc/generator/template/darkfish/fonts/SourceCodePro-Regular.ttf' from #{read pipe}#
killing process 8510
guix package: error: build failed: some substitutes for the outputs of derivation `/gnu/store/l7ffwqbkrvd4vk3h51p597psyl44gv67-ruby-2.3.0.drv' failed (usually happens due to networking issues); try `--fallback' to build derivation from source
next reply other threads:[~2016-03-23 23:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 23:48 Christopher Allan Webber [this message]
2016-03-24 13:25 ` bug#23103: A number of corrupt packages on Hydra? Pjotr Prins
2016-03-24 23:08 ` Pjotr Prins
2016-03-25 13:47 ` Ludovic Courtès
2016-03-26 23:24 ` Christopher Allan Webber
2016-03-27 21:22 ` Ludovic Courtès
2016-03-29 21:23 ` Leo Famulari
2016-04-03 8:20 ` Pjotr Prins
2016-04-03 10:55 ` Ben Woodcroft
2016-04-03 18:16 ` Leo Famulari
2016-04-03 20:42 ` Ludovic Courtès
2016-04-04 15:14 ` Pjotr Prins
2016-04-04 20:44 ` 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=87h9fwiwm5.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=23103@debbugs.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 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).