Hello Guix! ludo@gnu.org (Ludovic Courtès) skribis: > As of commit 608e42e7c92114497e7908980424288079acee1e, Guix builds with > Guile 2.2 (to be released sometime within the next 24 hours) and the > whole test suite passes. > > All the dependencies of Guix except Guile-SSH (optional; use for > offloading and for ‘guix copy’) are already compatible with Guile 2.2. With the attached patch, the ‘guix’ package is built against Guile 2.2. I’m running it on my GuixSD machine, and it works like a charm! 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 The fix is for ‘guix pull’ to build with Guile 2.2 when that’s what we’re running. For that, build-self.scm must be sure it can get the ‘guile2.2-ssh’ package when we’re on 2.2, or it will fail to compile the new Guix. However, ‘guile2.2-ssh’ appeared a day ago, so it’s missing from most installations… In short, ‘guix pull’ is broken in a way that may practically prevent it from handling the 2.0-to-2.2 transition. The risk is that ‘guix pull’ will fail to upgrade, preventing users from upgrading Guix altogether. To work around that, people will have to use a Git checkout of Guix. Of course that’s what many of us already do, but still. Maybe the upcoming release is a good time to make that transition: at least people installing GuixSD or Guix from that release will already be on 2.2 and won’t have problems from there on. Thoughts? Ideas? We all know it, but it’s really really time to fix ‘guix pull’… Ludo’.