all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Julien Lepiller <julien@lepiller.eu>
Cc: help-guix@gnu.org
Subject: Re: Updating a very old Guix
Date: Tue, 13 Nov 2018 15:05:30 +0100	[thread overview]
Message-ID: <m18t1x139x.fsf@ordinateur-de-catherine--konrad.home> (raw)
In-Reply-To: <ccc16b1c9b29940a4d302aebafbeec4b@lepiller.eu>

Hi Julien,

> The command you should run is:
>
> guix archive --recursive --export `readlink -f ~/.config/guix/current` > 
> guix-update.nar
>
> note the --recursive (so guix can find its dependencies, but it will 
> bundle every dependency in the .nar, so there may be some duplication 

I just tried that one - same problem with guix-authenticate.

> renamed the directory where the current guix version is installed). I 
> think I told you "latest" before, that was my mistake, sorry. Maybe you 
> can try again "guix copy", with "current" this time?

No change, I get the same protocol error.

I actually do have ~/.config/guix/latest (probably left over from an
older guix), and it does point to a store entry. So I should be able to
archive and copy it, even if it's not the entry that I need.

Cheers,
  Konrad.

  reply	other threads:[~2018-11-13 14:05 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
2018-11-13 12:53         ` Julien Lepiller
2018-11-13 14:05           ` Konrad Hinsen [this message]
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=m18t1x139x.fsf@ordinateur-de-catherine--konrad.home \
    --to=konrad.hinsen@fastmail.net \
    --cc=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    /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.