[debbugs-tracker] bug#18534: closed ("guix pull" may fail to build future versions of Guix)

[GNU bug Tracking System]

Your message dated Sun, 09 Nov 2014 22:38:44 +0100
with message-id <address@hidden>
and subject line Re: bug#18534: problems with "guix pull"
has caused the debbugs.gnu.org bug report #18534,
regarding "guix pull" may fail to build future versions of Guix
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
18534: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18534
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: problems with "guix pull"
>
>
>
>
> Date: 
>
> Tue, 23 Sep 2014 12:15:11 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.130011 (Ma Gnus v0.11) Emacs/24.3 (gnu/linux)
>
>
>
>
> Carlos Carleos <address@hidden> 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)
>
> [...]
>
> > address@hidden:~$ 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’.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#18534: problems with "guix pull"
>
>
>
>
> Date: 
>
> Sun, 09 Nov 2014 22:38:44 +0100
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
>
>
>
>
> address@hidden (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 <address@hidden> 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’.
>
>
> --- End Message ---