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.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 32018 in the body.
You can then email your comments to 32018 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#32018; Package guix. (Sat, 30 Jun 2018 11:54:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to swedebugia <swedebugia <at> riseup.net>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Sat, 30 Jun 2018 11:54:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: swedebugia <swedebugia <at> riseup.net>
To: "Bug-guix <at> gnu org" <Bug-guix <at> gnu.org>
Subject: Guixsd pull error on very old install
Date: Sat, 30 Jun 2018 13:53:12 +0200
[Message part 1 (text/plain, inline)]
Hi
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). 

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.

Stating this clearly help people know what to expect.

What do you think? 
-- 
Cheers Swedebugia 
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#32018; Package guix. (Mon, 02 Jul 2018 09:40:02 GMT) Full text and rfc822 format available.

Message #8 received at 32018 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: swedebugia <swedebugia <at> riseup.net>
Cc: 32018 <at> debbugs.gnu.org
Subject: Re: bug#32018: Guixsd pull error on very old install
Date: Mon, 02 Jul 2018 11:39:40 +0200
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.

> Stating this clearly help people know what to expect.

I agree.

Thanks,
Ludo’.




Information forwarded to bug-guix <at> gnu.org:
bug#32018; Package guix. (Fri, 13 Jul 2018 19:14:02 GMT) Full text and rfc822 format available.

Message #11 received at 32018 <at> debbugs.gnu.org (full text, mbox):

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: Re: 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.





Information forwarded to bug-guix <at> gnu.org:
bug#32018; Package guix. (Fri, 13 Jul 2018 20:44:01 GMT) Full text and rfc822 format available.

Message #14 received at 32018 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12 <at> thebird.nl>
Cc: swedebugia <swedebugia <at> riseup.net>, 32018 <at> debbugs.gnu.org
Subject: Re: bug#32018: Guixsd pull error on very old install
Date: Fri, 13 Jul 2018 22:42:54 +0200
Pjotr Prins <pjotr.public12 <at> thebird.nl> skribis:

> 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.

I agree, yes.  That’s a reasonable goal and one that should be easier to
achieve now with the new ‘guix pull’.

Note that swedebugia was talking of a pre-0.10 GuixSD, more than 2.5
years old, which represents a looong time for a pre-1.0 piece of
software that evolves pretty fast.  :-)

Thank you,
Ludo’.




Reply sent to swedebugia <at> riseup.net:
You have taken responsibility. (Mon, 17 Dec 2018 10:51:02 GMT) Full text and rfc822 format available.

Notification sent to swedebugia <swedebugia <at> riseup.net>:
bug acknowledged by developer. (Mon, 17 Dec 2018 10:51:02 GMT) Full text and rfc822 format available.

Message #19 received at 32018-done <at> debbugs.gnu.org (full text, mbox):

From: swedebugia <at> riseup.net
To: 32018-done <at> debbugs.gnu.org
Subject: Guixsd pull error on very old install
Date: Mon, 17 Dec 2018 02:50:25 -0800
Closed because I do not intend to investigate further and we do not
support pulling from too old guix versions because of our rapid dev
speed pre-1.0.

-- 
Cheers 
Swedebugia




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Mon, 14 Jan 2019 12:24:04 GMT) Full text and rfc822 format available.

This bug report was last modified 5 years and 97 days ago.

Previous Next


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