--- Begin Message ---
Subject: |
core-updates: url-fetch/tarbomb, url-fetch/zipbomb fail with "unbound variable: invoke" |
Date: |
Mon, 16 Apr 2018 20:54:39 -0500 |
In commit 20927c9331b493eaf94211ad9f8a5055e11b4588
url-fetch/tarbomb and url-fetch/zipbomb in guix/download.scm were
switched to use 'invoke' instead of 'system*'. On core-updates this
leads for me to an error when attempting to build the source for
packages that use these fetch methods. For example, font-text-gyre:
$ ./pre-inst-env guix build -S font-tex-gyre
The following derivation will be built:
/gnu/store/clxzrqzqbn182nrnkpabd8f4kqfw5bna-tg-2.005otf.zip.drv
@ build-started /gnu/store/clxzrqzqbn182nrnkpabd8f4kqfw5bna-tg-2.005otf.zip.drv
- x86_64-linux
/var/log/guix/drvs/cl//xzrqzqbn182nrnkpabd8f4kqfw5bna-tg-2.005otf.zip.drv.bz2
Backtrace:
3 (primitive-load "/gnu/store/c1r3fzw5mdh9hqydm2ri2rbdsib?")
In ice-9/eval.scm:
196:27 2 (_ #f)
223:20 1 (proc #<directory (guile-user) 7cc140>)
In unknown file:
0 (%resolve-variable (7 . invoke) #<directory (guile-user?>)
ERROR: In procedure %resolve-variable:
Unbound variable: invoke
note: keeping build directory `/tmp/guix-build-tg-2.005otf.zip.drv-2'
builder for `/gnu/store/clxzrqzqbn182nrnkpabd8f4kqfw5bna-tg-2.005otf.zip.drv'
failed with exit code 1
@ build-failed /gnu/store/clxzrqzqbn182nrnkpabd8f4kqfw5bna-tg-2.005otf.zip.drv
- 1 builder for
`/gnu/store/clxzrqzqbn182nrnkpabd8f4kqfw5bna-tg-2.005otf.zip.drv' failed with
exit code 1
guix build: error: build failed: build of
`/gnu/store/clxzrqzqbn182nrnkpabd8f4kqfw5bna-tg-2.005otf.zip.drv' failed
$
If I revert that commit it succeeds. I suppose the (guix build utils)
module needs to be imported into the builder.
`~Eric
pgpoWCvTJG1Vw.pgp
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#31187: core-updates: url-fetch/tarbomb, url-fetch/zipbomb fail with "unbound variable: invoke" |
Date: |
Thu, 19 Apr 2018 07:33:24 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) |
Hi Glenn,
Thanks very much for your informative message. I feel embarrassed for
not noticing that there were multiple pages. I rarely use the web
interface, and I guess the projects I've worked tend to have fewer than
400 active bugs.
Glenn Morris <address@hidden> writes:
> If Eric had used X-Debbugs-CC instead of Cc in the initial report, the
> mail you got would have included the bug number in the subject.
> I believe this is well documented (eg on the "how to report a bug"
> section on https://debbugs.gnu.org/).
Okay, I will try to remind people to use 'X-Debbugs-CC' instead of 'Cc'
in the future.
>> I've reported these problems to the FSF sysadmins, and I'd like to give
>> them an opportunity to diagnose the problem before we change the status
>> of this bug.
>
> The FSF sysadmins don't maintain debbugs.gnu.org, so the help-debbugs
> list would have been better. I (debbugs.gnu.org maintainer) happened to
> see your mail although I don't normally read bug-guix.
That was quite fortuitous. Thanks again!
I'm closing this bug now.
Mark
--- End Message ---