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

Previous Next

Full log

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

Previous Next

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