GNU bug report logs -
#18534
"guix pull" may fail to build future versions of Guix
Previous Next
Reported by: ludo <at> gnu.org (Ludovic Courtès)
Date: Tue, 23 Sep 2014 10:16:02 UTC
Severity: normal
Merged with 18887
Done: ludo <at> gnu.org (Ludovic Courtès)
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Sun, 09 Nov 2014 22:38:44 +0100
with message-id <87ppcwrr4r.fsf <at> gnu.org>
and subject line Re: bug#18534: problems with "guix pull"
has caused the debbugs.gnu.org bug report #18534,
regarding guix pull failed
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
18534: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18534
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Hello, folks.
I try to pull guix, but it is not work neither by root nor by user.
This is a output of `guix pull --verbose`
compiling
'/gnu/store/akma9bmmjnizkv9sj1669wa8x4abrzyp-guix-latest/guix/import/pypi.scm'...
ERROR: no code for module (json)
Backtrace:
In ice-9/boot-9.scm:
157: 12 [catch #t #<catch-closure 9ba5a0> ...]
In unknown file:
?: 11 [apply-smob/1 #<catch-closure 9ba5a0>]
In ice-9/boot-9.scm:
63: 10 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
432: 9 [eval # #]
In ice-9/boot-9.scm:
2401: 8 [save-module-excursion #<procedure 9d7880 at
ice-9/boot-9.scm:4045:3 ()>]
4050: 7 [#<procedure 9d7880 at ice-9/boot-9.scm:4045:3 ()>]
1724: 6 [%start-stack load-stack #<procedure 9ea840 at
ice-9/boot-9.scm:4041:10 ()>]
1729: 5 [#<procedure 9ecc60 ()>]
In unknown file:
?: 4 [primitive-load
"/gnu/store/2cfbcxyx6nc22v7raj3v094ky2544ks5-guix-latest-guile-builder"]
In ice-9/eval.scm:
387: 3 [eval # ()]
In
/gnu/store/n2jjh4kzfv3hp4zhd0aflwq4i2jihnnq-module-import/guix/build/pull.scm:
121: 2 [build-guix
"/gnu/store/akma9bmmjnizkv9sj1669wa8x4abrzyp-guix-latest" ...]
75: 1 [p-for-each #<procedure d690c0 at
/gnu/store/n2jjh4kzfv3hp4zhd0aflwq4i2jihnnq-module-import/guix/build/pull.scm:121:14
(file)> ...]
In unknown file:
?: 0 [scm-error misc-error #f ...]
ERROR: In procedure scm-error:
ERROR: process failed #<procedure d690c0 at
/gnu/store/n2jjh4kzfv3hp4zhd0aflwq4i2jihnnq-module-import/guix/build/pull.scm:121:14
(file)> 256
builder for
`/gnu/store/0nji4jqs90lvm8sbx5j8iwfwl4fqpir7-guix-latest.drv' failed
with exit code 1
guix pull: error: build failed: build of
`/gnu/store/0nji4jqs90lvm8sbx5j8iwfwl4fqpir7-guix-latest.drv' failed
[Message part 3 (message/rfc822, inline)]
ludo <at> gnu.org (Ludovic Courtès) skribis:
> The old ‘guix pull’ didn’t now about the gnu.scm file, hence the error
> (this was fixed in June, in commit 9d0b8fbd.)
>
> That means you have to actually run ‘guix pull’ from 0.7, or from a
> recent checkout.
>
> The fact that ‘guix pull’ can potentially break for some future version
> is unfortunate. It would be ideal if instead of using its own build
> recipe, it would use one from the tarball.
[...]
> Igor Gajsin <igajsin <at> mirantis.com> skribis:
>
> > This is a output of `guix pull --verbose`
> >
> > compiling
> > /gnu/store/akma9bmmjnizkv9sj1669wa8x4abrzyp-guix-latest/guix/import/pypi.scm'...
> > ERROR: no code for module (json)
>
> For now, this problem can be worked around as described here:
>
> http://lists.gnu.org/archive/html/guix-devel/2014-09/msg00488.html
This bug should be fixed by f81ac34.
The idea is that the build recipe that is executed is now taken from the
newly-downloaded Guix. Before that, we would use the build recipe from
whatever Guix version was running, hence this kind of problems.
Comments and testing welcome!
Thanks,
Ludo’.
This bug report was last modified 10 years and 225 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.