From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Paul Garlick <pgarlick@tourbillion-technology.com>, help-guix@gnu.org
Subject: Re: Stuck upgrading from Guix v0.12
Date: Mon, 17 Dec 2018 15:27:37 +0100 [thread overview]
Message-ID: <m14lbcp6sm.fsf@fastmail.net> (raw)
In-Reply-To: <1545049789.2673.17.camel@tourbillion-technology.com>
Hi Paul,
> A lesson learnt from a previous update process [1] was; do not leave it
> too long between 'guix pull' updates.
>
> However, I have one system running Ubuntu 16.04 and Guix v0.12 that I
> am trying to update. As root:
I have had similar problems as well in the past. The one recipe that has
always worked (aside from one case of a machine with very limited disk
space) is temporarily using a Guix compiled from source code.
The procedure for building Guix from source code is explained in the manual:
https://www.gnu.org/software/guix/manual/en/html_node/Building-from-Git.html#Building-from-Git
When done (it takes a while to compile), run that copy of Guix to do a
"guix pull", without installing it, as described in
https://www.gnu.org/software/guix/manual/en/html_node/Running-Guix-Before-It-Is-Installed.html#Running-Guix-Before-It-Is-Installed
After that, your standard Guix installation is up to date and you can
delete all the source code again.
The procedure is lengthy in terms of compile time, and requires a lot of
temporary disk space, but the advantage is that you don't have to
analyze what actually went wrong with your installation. Put
differently, it's hard on your computer but easy on our brain :-)
Konrad.
next prev parent reply other threads:[~2018-12-17 14:27 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 [this message]
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
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=m14lbcp6sm.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=help-guix@gnu.org \
--cc=pgarlick@tourbillion-technology.com \
/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.