From: Leo Famulari <leo@famulari.name>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: Harry Prevor <habs@sdf.org>, 24220@debbugs.gnu.org
Subject: bug#24220: "failed to unpack source code" on guix pull
Date: Sun, 14 Aug 2016 12:21:23 -0400 [thread overview]
Message-ID: <20160814162123.GB1197@jasmine> (raw)
In-Reply-To: <87r39rrajs.fsf@we.make.ritual.n0.is>
On Sun, Aug 14, 2016 at 08:59:03AM +0000, ng0 wrote:
> Pjotr Prins <pjotr.public12@thebird.nl> writes:
> > 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?
>
> This was caused by a patch I sent which was applied on master.
> Guix error messages could be more natural, as for me the error output I
> got seemed just verbose and I decided it was okay to send this in. The
> commit has since then be reverted and I will send in an updated patch.
>
> Simpler explanation: a license I added was already inherited by another
> loaded module, this caused some "hick up" and make broke (while it did
> not break locally on my side).
I don't think this is the cause of this bug.
If I remember correctly, Harry mentioned this bug on IRC before the
"expat" problem. Also, this problem appears to happen while unpacking
the tarball, and I _think_ that should be possible independent of bugs
in Guix code.
Since nobody has suggested a more precise debugging method, I recommend
you try running the guix-daemon with `strace -f -o logfile` to see
precisely what fails.
next prev parent reply other threads:[~2016-08-14 16:22 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
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 [this message]
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=20160814162123.GB1197@jasmine \
--to=leo@famulari.name \
--cc=24220@debbugs.gnu.org \
--cc=habs@sdf.org \
--cc=ng0@we.make.ritual.n0.is \
/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).