all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org
Subject: Re: Updating a very old Guix
Date: Fri, 09 Nov 2018 15:51:28 +0100	[thread overview]
Message-ID: <2adb18453b8eb8bab85b6ac07f806eb2@lepiller.eu> (raw)
In-Reply-To: <m136sauxjf.fsf@khs-macbook.home>

Le 2018-11-09 15:37, Konrad Hinsen a écrit :
> Hi everyone,
> 
> I have a computer that I don't use very often, with a rather old Guix
> installation from nearly a year ago. So I though I should do an update.
> 
> First try: "guix pull".
> 
> Does a lot of downloading and compiling, then finishes. But guix no
> longer works:
> 
>    ERROR: In procedure scm-error:
>    no code for module (gcrypt hash)
> 
> Next try: I cloned the repository under a different user account (that
> still had the old Guix). "guix environment guix", "bootstrap", and
> then "configure" get me to the error message:
> 
>   configure: error: A recent Guile-SQLite3 could not be found; please
>   install it.
> 
> But I cannot install a recent Guile-SQLite3 without doing a "guix pull"
> first.
> 
> One more option I can think of is installing everything required to
> compile Guix manually, then compile from source. Not exactly an
> attractive idea, all the more since the dependency list in the Guix
> manual looks incomplete (it doesn't mention Guile, for example, nor
> Guile-SQLite3).
> 
> Are there any other options ? I would like to avoid deleting everything
> and starting from scratch because there is one account on that machine
> that has in its Guix profile my only working installation of the only
> program I actually need this machine for.
> 
> Konrad.

If you have another machine with guix installed, you could try to use 
guix copy to copy a working guix pull profile (~/.config/guix/current) 
to that computer, and then you will be able to use that guix to run guix 
pull. Don't forget to create a key-pair on the other machine and to 
authorize the public key on the receiving end.

So on a machine with a recent guix:

guix archive --generate-key
scp /etc/guix/signing-key.pub remote@machine

On the first machine:

guix archive --authorize < signing-key.pub

On the machine with a recent guix:

guix copy --to=remote@machine `readlink -f ~/.config/guix/latest`

And finally on the machine with an old guix:

/gnu/store/.../bin/guix pull
# with ... the result of readlink on the machine with the recent guix.

Hopefully, that will work :)

See 
http://guix.info/manual/en/Invoking-guix-copy.html#Invoking-guix-copy 
and 
http://guix.info/manual/en/Invoking-guix-archive.html#Invoking-guix-archive 
for reference.

  reply	other threads:[~2018-11-09 14:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 14:37 Updating a very old Guix Konrad Hinsen
2018-11-09 14:51 ` Julien Lepiller [this message]
2018-11-09 16:26 ` swedebugia
2018-11-09 17:07   ` Konrad Hinsen
2018-11-09 18:27     ` znavko
2018-11-10 10:52       ` Konrad Hinsen
2018-11-10 10:51     ` Konrad Hinsen
2018-11-12 19:37     ` swedebugia
2018-11-13 12:43       ` Konrad Hinsen
2018-11-13 12:53         ` Julien Lepiller
2018-11-13 14:05           ` Konrad Hinsen
2018-11-13 16:00         ` swedebugia
2018-11-14 15:21           ` Konrad Hinsen
2018-11-15 12:41             ` swedebugia
2018-11-17 12:42               ` Konrad Hinsen

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=2adb18453b8eb8bab85b6ac07f806eb2@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=help-guix@gnu.org \
    /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.