From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Harry Prevor <habs@sdf.org>
Cc: 24220@debbugs.gnu.org
Subject: bug#24220: "failed to unpack source code" on guix pull
Date: Sun, 14 Aug 2016 07:27:35 +0200 [thread overview]
Message-ID: <20160814052735.GA13020@thebird.nl> (raw)
In-Reply-To: <f841fc28abf6b4177e8b56bbf1a8a6c7@sdf.org>
On Sat, Aug 13, 2016 at 06:05:17PM -0400, Harry Prevor wrote:
> Hey all,
>
> I'm running GuixSD on a Thinkpad X200. I typically run 'guix pull'
> almost every day without any troubles, but about two days ago I
> started getting this error every time I ran the command leaving me
> unable to update my system:
>
> >Starting download of /tmp/guix-file.JNdnA7
> >From
> >http://git.savannah.gnu.org/cgit/guix.git/snapshot/master.tar.gz...
> > ….tar.gz 1.4MiB/s 00:07 |
> >10.4MiB transferred
> >unpacking
> >'/gnu/store/q4zzpxpbbhwmwh4snisymlpf0p24ddk7-guix-latest.tar.gz'...
> >guix pull: error: failed to unpack source code
>
> What's odd about this, is the actual file
> /gnu/store/q4z...-guix-latest.tar.gz, appears to be a valid targz
> archive, and I'm able to unpack and repack that using tar manually
> just fine. 'realpath $(which tar)' returns
> '/gnu/store/ggmmcw327ny831gqd7zvi3hpl5fm23mn-tar-1.28/bin/tar', and
> I've done some basic tests which do confirm that binary seems to
> work. I'm not having any network problems otherwise.
>
> What can I do to further debug / fix this?
>
> P.S. I'm not subscribed to bug-guix, so please CC me in any
> responses to this thread!
I also saw this bug yesterday. Reminds me how luxurious GNU Guix
normally is - for several things to fail at the same time is rare.
next prev parent reply other threads:[~2016-08-14 5:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 22:05 bug#24220: "failed to unpack source code" on guix pull Harry Prevor
2016-08-14 5:27 ` Pjotr Prins [this message]
2016-08-14 8:59 ` ng0
2016-08-14 13:02 ` Harry Prevor
2016-08-14 14:27 ` ng0
2016-08-14 16:21 ` Leo Famulari
2016-08-22 15:49 ` Harry Prevor
2019-02-13 0:29 ` Leo Famulari
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=20160814052735.GA13020@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=24220@debbugs.gnu.org \
--cc=habs@sdf.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).