From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#31085: Unexpected behaviour when running `guix build lilypond' Date: Mon, 23 Apr 2018 15:26:24 +0200 Message-ID: <87in8i12bj.fsf@gnu.org> References: <873708jdao.fsf@GlaDOS.home> <87muxzi4v4.fsf@gnu.org> <87tvs5tw1q.fsf@GlaDOS.home> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34256) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fAbUo-0001is-GZ for bug-guix@gnu.org; Mon, 23 Apr 2018 09:27:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fAbUk-0001Jo-Fu for bug-guix@gnu.org; Mon, 23 Apr 2018 09:27:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:56949) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fAbUk-0001Jf-Ck for bug-guix@gnu.org; Mon, 23 Apr 2018 09:27:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fAbUk-0005Bd-5r for bug-guix@gnu.org; Mon, 23 Apr 2018 09:27:02 -0400 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: In-Reply-To: <87tvs5tw1q.fsf@GlaDOS.home> (Diego Nicola Barbato's message of "Fri, 20 Apr 2018 23:20:01 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Diego Nicola Barbato Cc: 31085-done@debbugs.gnu.org Hi, Diego Nicola Barbato skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > >> Hello, >> >> Diego Nicola Barbato skribis: >> >>> I have experienced some unexpected behaviour when running `guix build >>> lilypond': >>> After verifying that there was a substitute available with `guix weather >>> -m m.scm' (Where m.scm evaluates to a manifest containing only lilypond) >>> I ran `guix build lilypond --dry-run' which claimed that a substitute >>> would be downloaded. I then ran `guix build lilypond' which proceeded >>> to build lilypond from source (instead of downloading the substitute). >>> >>> Upon explaining this on IRC it was suggested that I try running `guix >>> build --no-grafts lilypond' (which actually downloaded the substitute) >>> then deleting the locally built lilypond with `guix gc --delete >>> /gnu/store/...' and finally running `guix build lilypond' again (which, >>> this time, grafted the substituted lilypond instead of building it from >>> source again). While this fixed the issue I was told that this >>> behaviour was indeed unexpected. >> >> We=E2=80=99d have to see if this is still reproducible, but I have a pla= usible >> explanation. > > I can consistently reproduce this in a VM with the following steps: > > First I run: > > $ qemu-system-x86_64 -enable-kvm -snapshot -m 4G $(guix system vm-image = bare-bones.scm --image-size=3D8G) > > (Where bare-bones.scm is the bare-bones.tmpl after replacing /dev/sdX > with /dev/sda.) > > Then after logging in as root: > > # guix pull --commit=3D872bda5de52a8f0514230ebc4e9680aab74f509a > # guix build --dry-run lilypond > > Which returns: > > 52.1 MB would be downloaded: > /gnu/store/0amx7bcbs518lkqwfh2azmqrp2yqib0g-lilypond-2.19.80 > /gnu/store/7b5ykfl6jbrdl8j7xp630fga4as3234z-ghostscript-9.22 > /gnu/store/j4vj7h3wyb532g2j0axzjj43z2a0dg81-python-2.7.14 > /gnu/store/k2ak44m0miind785x22mmpbcwi0mq7hq-freetype-2.8.1 > /gnu/store/mkhfqx7m7pniyic0kh0lnafmajymn4dr-guile-1.8.8 > /gnu/store/pwbx5fhjrq9crr1c0d2x08ch0l6vr3cv-pango-1.40.14 > /gnu/store/qm8ri32n0rkh749v3jb3x8s8ksjl7yd3-fontconfig-2.12.6 > /gnu/store/sm37m59gq3smxxz8gs4jikn50qg0g7xh-glib-2.54.2 > > Then: > > # guix build lilypond > > Which, after downloading the dependencies, starts to build lilypond from > source. I could reproduce it. This is fixed by commit 5e5d6613a3837586ccab51cd988b44c7df99253b. The story is quite surprising: the =E2=80=98font-tex-gyre=E2=80=99 packages= uses =E2=80=98url-fetch/zipbomb=E2=80=99. =E2=80=98url-fetch/zipbomb=E2=80=99 r= efers to unzip to do its job. With grafts enabled, =E2=80=98url-fetch/zipbomb=E2=80=99 would use a = grafted unzip, leading to a different /gnu/store/=E2=80=A6-tg-2.005otf.zip than when grafts are disabled. Consequently, the base lilypond.drv would already depend on whether or not grafts are enabled. When grafts are enabled, you would end up having to build a lilypond that=E2=80=99s different from what =E2=80=9Cguix= build lilypond --no-grafts=E2=80=9D builds because of this. I hope this explanation makes any sense but anyway, it=E2=80=99s fixed now.= :-) Thanks, Ludo=E2=80=99.