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

Previous Next

Package: guix;

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.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 18534 in the body.
You can then email your comments to 18534 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#18534; Package guix. (Tue, 23 Sep 2014 10:16:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to ludo <at> gnu.org (Ludovic Courtès):
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Tue, 23 Sep 2014 10:16:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

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




Changed bug title to '"guix pull" may fail to build future versions of Guix' from 'problems with "guix pull"' Request was from ludo <at> gnu.org (Ludovic Courtès) to control <at> debbugs.gnu.org. (Wed, 24 Sep 2014 12:18:02 GMT) Full text and rfc822 format available.

Merged 18534 18887. Request was from ludo <at> gnu.org (Ludovic Courtès) to control <at> debbugs.gnu.org. (Wed, 29 Oct 2014 22:50:01 GMT) Full text and rfc822 format available.

Reply sent to ludo <at> gnu.org (Ludovic Courtès):
You have taken responsibility. (Sun, 09 Nov 2014 21:39:02 GMT) Full text and rfc822 format available.

Notification sent to ludo <at> gnu.org (Ludovic Courtès):
bug acknowledged by developer. (Sun, 09 Nov 2014 21:39:03 GMT) Full text and rfc822 format available.

Message #14 received at 18534-done <at> debbugs.gnu.org (full text, mbox):

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




Reply sent to ludo <at> gnu.org (Ludovic Courtès):
You have taken responsibility. (Sun, 09 Nov 2014 21:39:03 GMT) Full text and rfc822 format available.

Notification sent to Igor Gajsin <igajsin <at> mirantis.com>:
bug acknowledged by developer. (Sun, 09 Nov 2014 21:39:04 GMT) Full text and rfc822 format available.

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Mon, 08 Dec 2014 12:24:03 GMT) Full text and rfc822 format available.

This bug report was last modified 9 years and 113 days ago.

Previous Next


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