[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 0/1] Help wanted fixing a ruby-minitar bug
From: |
Ludovic Courtès |
Subject: |
Re: [PATCH 0/1] Help wanted fixing a ruby-minitar bug |
Date: |
Tue, 24 Jan 2017 22:40:20 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Leo Famulari <address@hidden> skribis:
> I tried using this patch to fix a bug in ruby-minitar, but the build
> fails as shown below. Any ideas?
>
> $ ./pre-inst-env guix build ruby-minitar
> The following derivations will be built:
> /gnu/store/naprvm320mvzlhv4ciax0436qqm3r8zj-ruby-minitar-0.5.4.drv
> /gnu/store/vz70g01wln7aflljz65yf425pppcgpjd-minitar-0.5.4.tar.xz.drv
> @ build-started
> /gnu/store/vz70g01wln7aflljz65yf425pppcgpjd-minitar-0.5.4.tar.xz.drv -
> x86_64-linux
> /var/log/guix/drvs/vz//70g01wln7aflljz65yf425pppcgpjd-minitar-0.5.4.tar.xz.drv.bz2
> data.tar.gz
> metadata.gz
> source is under 'data.tar.gz'
[...]
> ?: 0 [chdir "data.tar.gz"]
This is apparently a “tarbomb”: it unpacks more than one file in $PWD.
The ‘first-subdirectory’ procedure in gnu-build-system.scm is a bit
stupid and takes the first file in $PWD as the directory to cd to.
To work around that, use ‘url-fetch/tarbomb’.
HTH!
Ludo’.