GNU bug report logs - #18534
"guix pull" may fail to build future versions of Guix

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: ludo <at> gnu.org (Ludovic Courtès)
Subject: bug#18534: closed (Re: bug#18534: problems with "guix pull")
Date: Sun, 09 Nov 2014 21:39:03 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#18534: "guix pull" may fail to build future versions of Guix

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 18534 <at> debbugs.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)]

From: ludo <at> gnu.org (Ludovic Courtès)
To: Carlos Carleos <carleos <at> uniovi.es>, Igor Gajsin <igajsin <at> mirantis.com>
Cc: guix-devel <at> gnu.org, 18534-done <at> debbugs.gnu.org
Subject: Re: bug#18534: problems with "guix pull"
Date: Sun, 09 Nov 2014 22:38:44 +0100

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’.

[Message part 3 (message/rfc822, inline)]

From: ludo <at> gnu.org (Ludovic Courtès)
To: Carlos Carleos <carleos <at> uniovi.es>
Cc: guix-devel <guix-devel <at> gnu.org>, bug-guix <at> gnu.org
Subject: Re: problems with "guix pull"
Date: Tue, 23 Sep 2014 12:15:11 +0200

Carlos Carleos <carleos <at> uniovi.es> skribis:

> Hi!  On a Ubuntu system I've tried "sudo guix pull --verbose" and obtained this
> ([...] used to shorten the output; warnings and errors left):

[...]

> compiling '/gnu/store/8s2y6886rl6z79axbskyh17xd18xw5cq-guix-latest/gnu/packages/abiword.scm'...
> [...]
> compiling '/gnu/store/8s2y6886rl6z79axbskyh17xd18xw5cq-guix-latest/gnu/services/xorg.scm'...
> compiling '/gnu/store/8s2y6886rl6z79axbskyh17xd18xw5cq-guix-latest/gnu/system.scm'...
> compiling '/gnu/store/8s2y6886rl6z79axbskyh17xd18xw5cq-guix-latest/gnu/system/file-systems.scm'...
> compiling '/gnu/store/8s2y6886rl6z79axbskyh17xd18xw5cq-guix-latest/gnu/system/grub.scm'...
> compiling '/gnu/store/8s2y6886rl6z79axbskyh17xd18xw5cq-guix-latest/gnu/system/install.scm'...
> ERROR: no code for module (gnu)

[...]

> carleos <at> carleos:~$ guix --version
> guix (GNU Guix) 0.6

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.

I’ll see how this can be fixed.

(Cc: bug-guix so the bug is recorded.)

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.