all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org, Paul Garlick <pgarlick@tourbillion-technology.com>
Subject: Re: Stuck upgrading from Guix v0.12
Date: Wed, 19 Dec 2018 14:57:31 +0100	[thread overview]
Message-ID: <87zht1wrec.fsf@gnu.org> (raw)
In-Reply-To: <87ftuvvkxt.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 17 Dec 2018 23:37:50 +0100")

Heya,

Ricardo Wurmus <rekado@elephly.net> skribis:

> I’m in the same situation upgrading a machine that didn’t have an
> Internet connection for months.
>
> Here’s what I do:
>
> - use a git checkout to jump to commit
>   b0cb92b2d43a2c4d5fa9b3f8c04c5732c60061e7, which adds guile-gcrypt
>
> - ./bootstrap && ./configure --localstatedir=/var && make clean && make
>
> - ./pre-inst-env guix package -i guile guile-sqlite3 guile-json
>   guile-ssh guile-gcrypt
>
> - update to the latest version

Just a reminder so people don’t run away ;-): the upgrade story got much
better shortly before 0.15.0, when ‘guix pull’ got the ability to “build
Guix from Guix” in a way that does not rely* on the currently installed
Guix.  For example, you can run 0.15’s ‘guix pull’ and upgrade to
today’s Guix without problems.

Ludo’.

* More specifically, ‘guix pull’ relies on a small subset of Guix
  functionality that hasn’t changed in a couple of years, which is a lot
  given Guix’s history.

  reply	other threads:[~2018-12-19 13:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 12:29 Stuck upgrading from Guix v0.12 Paul Garlick
2018-12-17 14:27 ` Konrad Hinsen
2018-12-17 14:52   ` Paul Garlick
2018-12-17 15:07     ` Gábor Boskovits
2018-12-17 22:37     ` Ricardo Wurmus
2018-12-19 13:57       ` Ludovic Courtès [this message]
2018-12-19 14:26         ` Ricardo Wurmus
2018-12-20 19:54           ` Paul Garlick
2019-01-09 16:47           ` Paul Garlick
2019-01-31 14:46             ` 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=87zht1wrec.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=pgarlick@tourbillion-technology.com \
    --cc=rekado@elephly.net \
    /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.