all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: swedebugia <swedebugia@riseup.net>,
	Julien Lepiller <julien@lepiller.eu>,
	help-guix@gnu.org
Subject: Re: Updating a very old Guix
Date: Tue, 13 Nov 2018 13:43:20 +0100	[thread overview]
Message-ID: <m1in11172v.fsf@fastmail.net> (raw)
In-Reply-To: <862f79ed-d84d-122d-e83f-8910b7c57777@riseup.net>

swedebugia <swedebugia@riseup.net> writes:

> This is most probably not correct. You most probably do have a working 
> Guix in the store but your current guix points to the new one which 
> lacks guile-gcrypt.

Indeed, kind of. It looks more complicated than that.

As you say, there is indeed a working guix in the store, but calling
apparently still makes it use the messed-up code under ~/.config/guix.
After renaming this to move it out of the way, I can again run guix
commands.

However...

> I suggest you roll back your guix pull profile following the manual. 
> (this might not work if your guix is too old)

My guix does seem to be too old for that. And while I can now invoke it
without an immediate error message, every attempt at installing or even
removing packages leads to an attempt to compile the GCC toolchain,
which fails for lack of disk space (there's only one 10 GB partition).


So I tried Julien's suggestion to copy over a newer guix from another
machine.

Step by step:

   guix archive --generate-key

Works fine, but must be run as root because it writes to /etc.

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

then on the remote machine

   guix archive --authorize < signing-key.pub

Again "guix archive" must be run as root. Back to the "new-guix" machine:

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

guix copy: error: failed to connect to `#<input-output: channel (open)
c7ed00>': Protocol error

Hard to say which protocol is not respected there, but given how old my
guix is, I suspect the protocol used by "guix copy" has changed since.

So let's try a variant: use "guix archive" to export a nar file, copy it
over to the other machine, and import it.

   guix archive --export `readlink -f ~/.config/guix/latest` > guix-update.nar

guix archive: error: build failed: program `guix-authenticate' failed
with exit code 1

There isn't much documentation on "guix authenticate" and how it might
fail, so I'll end my experiments here. Does anyone have an idea for
something else that I might try?

Cheers,
  Konrad.

  reply	other threads:[~2018-11-13 12:43 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
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 [this message]
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=m1in11172v.fsf@fastmail.net \
    --to=konrad.hinsen@fastmail.net \
    --cc=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=swedebugia@riseup.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.