On 05/09/2017 at 23:22 Ludovic Courtès writes:
> Hello Guix!
>
> l...@gnu.org (Ludovic Courtès) skribis:
>
>> There’s a problem though, called “guix pull”. ~/.config/guix/latest
>> currently contains 2.0 .go files. Thus after reconfiguring GuixSD to
>> use Guix-for-2.2, running ‘guix’ typically gives loads of warnings like:
>>
>> ;;; WARNING: loading compiled file
>> /home/ludo/.config/guix/latest/guix/derivations.go failed:
>> ;;; ERROR: In procedure load-thunk-from-memory: No such file or directory
>
> With commit 838ba73d6e49bd2b1f2d4ed9329b65cc4e8c1f54, ‘guix pull’ builds
> with the currently used Guile, be it 2.0 or 2.2. To achieve that, it
> tries hard to pick 2.0 or 2.2 packages for the dependencies of Guix.
>
> If it cannot find a “guile-ssh” package for the Guile being used (for
> instance, you’re using Guile 2.2 but lacking the “guile-ssh” package
> built with 2.2), then it simply skips modules that depend on Guile-SSH;
> they are optional anyway. For Guile-JSON, it just assumes that there is
> a matching Guile-JSON, which should be the case anyway.
>
> As I wrote before, ‘guix pull’ in its current form is pretty fragile;
> please report any problems you have.
>
>
> In addition, with commit 7561881f2a5d2dc463c24713745eca03e67044bf, the
> “guix” package is now built with Guile 2.2 instead of 2.0. Thus, next
> time you update GuixSD, /run/current-system/profile/bin/guix will be
> using Guile 2.2. At that point, if ~/.config/guix/latest contains .go
> files for 2.0, you’ll get warnings as shown above, and you’ll have to
> “guix pull” to get rid of them.
>
>
> At this point, we’re still using Guile 2.0 (1) to build derivations, and
> (2) in the Shepherd, mcron, and modules imported inside the Shepherd.
> In ‘core-updates’ we have addressed #1 and we’ll address #2 as well.
>
> Ludo’.
Hi Ludo, this sounds great!
I run GuixSD from git checkout this way ...
cd ~/src/guix
guix environment -e "(@ (gnu packages package-management) guix)" -M 4 \
-c 4
git pull
make clean-go
./bootstrap
./configure --localstatedir=/var --sysconfdir=/etc
make -j 10 check
exit
sudo guix system build /root/con/55.scm -M 4 -c 4
sudo guix system reconfigure /root/con/55.scm -M 4 -c 4
sudo reboot
Should this just work? Or is there something that needs to be done
differently for the 2.0 >>> 2.2 change?
TIA - George
