all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Garlick <pgarlick@tourbillion-technology.com>
To: "Ricardo Wurmus" <rekado@elephly.net>, "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Stuck upgrading from Guix v0.12
Date: Wed, 09 Jan 2019 16:47:56 +0000	[thread overview]
Message-ID: <a8b34d8cc94a05ef68d1b2147936600d96687c0e.camel@tourbillion-technology.com> (raw)
In-Reply-To: <87h8f9tx3d.fsf@elephly.net>

Hi Guix,

Got it! I have been able to upgrade from version 0.12 to version 0.16.

I used 'guix copy' to copy a recent guix on a local server.  Thank you
Gabor for the suggestion.  The steps I followed were:

i) generate signing keys on both systems
ii) copy across public keys and authorize on each system
iii) install guix in the user profile on the server
iv) use 'guix copy --from=localServer /gnu/store/...guix-0.16.0-4...'
Note: this copies the dependencies too
v) set GUILE_LOAD_PATH and GUILE_LOAD_COMPILED_PATH on the receiving
system.  Note: set the variables to point to the newly-copied paths in
/gnu/store for guile-gcrypt, guile-sqlite3, guile-git and guile-
bytestructures
vi) use '/gnu/store/...guix-0.16.0-4.../bin/guix pull'
vii) include .config/guix/current/bin in PATH variable
viii) use 'guix package --upgrade'
ix) update guix-daemon.service
x) restart daemon

To finish, I authorized substitutes for ci.guix.info.pub.  I am cooking
with gas again!

Best regards,

Paul.

  parent reply	other threads:[~2019-01-09 16:48 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
2018-12-19 14:26         ` Ricardo Wurmus
2018-12-20 19:54           ` Paul Garlick
2019-01-09 16:47           ` Paul Garlick [this message]
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=a8b34d8cc94a05ef68d1b2147936600d96687c0e.camel@tourbillion-technology.com \
    --to=pgarlick@tourbillion-technology.com \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    --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.