From: Leo Famulari <leo@famulari.name>
To: Nils Gillmann <niasterisk@grrlz.net>
Cc: 22573@debbugs.gnu.org
Subject: bug#22573: critical error during 'guix pull'
Date: Sat, 6 Feb 2016 15:53:17 -0500 [thread overview]
Message-ID: <20160206205317.GA6348@jasmine> (raw)
In-Reply-To: <87bn7tucvf.fsf@grrlz.net>
On Sat, Feb 06, 2016 at 03:33:56PM +0100, Nils Gillmann wrote:
> Hi, today 15:30 EU/Berlin Timezone I started guix pull and got this output:
>
> Starting download of /tmp/guix-file.bHtiW7
> From http://git.savannah.gnu.org/cgit/guix.git/snapshot/master.tar.gz...
> master.tar.gz 1KiB 2.5MiB/s 00:00 [####################] 100.0%
> unpacking '/gnu/store/ig37bb33y7vnpay722b541ljlqvmyjbm-guix-latest.tar.gz'...
>
> gzip: stdin: not in gzip format
> /gnu/store/9m8jg38cy0j95cb1gmi784ms85nn68vr-tar-1.28/bin/tar: Child returned status 1
> /gnu/store/9m8jg38cy0j95cb1gmi784ms85nn68vr-tar-1.28/bin/tar: Error is not recoverable: exiting now
> guix pull: error: failed to unpack source code
Since the capabilities of hydra.gnu.org are sometimes outstripped by
user demand, users sometimes experience repeatable network failures
while downloading. We have raised the funds to buy a more powerful
machine for hydra.gnu.org and to host it.
Do you know if this succeeded for you during the period while the Guix
git repository's HEAD was unchanged? Althought, I don't see how state of
HEAD could make a difference to whether or not the gzip encoding was
successful.
>
> --
> ng/ni*
> vcard: http://krosos.sdf.org
>
>
>
next prev parent reply other threads:[~2016-02-06 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 14:33 bug#22573: critical error during 'guix pull' Nils Gillmann
2016-02-06 20:53 ` Leo Famulari [this message]
2016-02-06 21:19 ` Nils Gillmann
2016-02-06 22:20 ` Leo Famulari
2016-02-07 19:34 ` Ludovic Courtès
2016-02-07 1:08 ` bug#22573: closed Nils Gillmann
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=20160206205317.GA6348@jasmine \
--to=leo@famulari.name \
--cc=22573@debbugs.gnu.org \
--cc=niasterisk@grrlz.net \
/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).