Carlos Carleos <carl...@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@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’.
