all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: 32018@debbugs.gnu.org
Subject: bug#32018: Guixsd pull error on very old install
Date: Fri, 13 Jul 2018 22:42:54 +0200	[thread overview]
Message-ID: <877elyeuk1.fsf@gnu.org> (raw)
In-Reply-To: <20180713191256.r5ak5gbeo37fuej3@thebird.nl> (Pjotr Prins's message of "Fri, 13 Jul 2018 21:12:56 +0200")

Pjotr Prins <pjotr.public12@thebird.nl> skribis:

> On Mon, Jul 02, 2018 at 11:39:40AM +0200, Ludovic Courtès wrote:
>> Hello,
>> 
>> swedebugia <swedebugia@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	other threads:[~2018-07-13 20:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30 11:53 bug#32018: Guixsd pull error on very old install swedebugia
2018-07-02  9:39 ` Ludovic Courtès
2018-07-13 19:12   ` Pjotr Prins
2018-07-13 20:42     ` Ludovic Courtès [this message]
2018-12-17 10:50 ` swedebugia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877elyeuk1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=32018@debbugs.gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.