GNU bug report logs - #32018
Guixsd pull error on very old install

Previous Next

Package: guix;

Reported by: swedebugia <swedebugia <at> riseup.net>

Date: Sat, 30 Jun 2018 11:54:01 UTC

Severity: normal

Done: swedebugia <at> riseup.net

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Pjotr Prins <pjotr.public12 <at> thebird.nl>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: swedebugia <swedebugia <at> riseup.net>, 32018 <at> debbugs.gnu.org
Subject: bug#32018: Guixsd pull error on very old install
Date: Fri, 13 Jul 2018 21:12:56 +0200
On Mon, Jul 02, 2018 at 11:39:40AM +0200, Ludovic Courtès wrote:
> Hello,
> 
> swedebugia <swedebugia <at> riseup.net> skribis:
> 
> > Trying to get an updated an old GuixSD installation via guix pull on a pre 0.10 GuixSD returned an error message about gexp-modules not found. (details can be provided if asked). 
> 
> Could you post the full backtrace?
> 
> > I suggest we either test pulling from old versions (and fix errors) or make it clear in the manual that pulling from very old GuixSD (older than 0.12?) is not supported.
> 
> Pulling from a very old Guix may not work.  We try hard to keep things
> running, but the old ‘guix pull’ had defects, plus the file
> build-aux/build-self.scm (which ‘guix pull’ runs) might use features not
> found in very old versions.

How about making sure that 'guix pull' works between major releases?
That should be reasonably easy to test.

When there is a disruptive release for guix pull make sure the user
upgrades to the closest previous release first. I.e., multi-step
releases are less fraught with breakage.

That way you get an incremental path to upgrade. And you only need to
test between major releases.

Pj.





This bug report was last modified 6 years and 241 days ago.

Previous Next


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