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: Wed, 14 Nov 2018 16:21:35 +0100	[thread overview]
Message-ID: <m1a7mbznuo.fsf@fastmail.net> (raw)
In-Reply-To: <f2960fd9-fac5-9439-5762-0124162fcc52@riseup.net>

swedebugia <swedebugia@riseup.net> writes:

> Could you report this to bug-guix@gnu.org?

Done (and Ludo and Ricardo are already looking into this).

> How about reinstalling v. 0.15 overwriting your current installation?
>
> this would invalidate all your store items though.

Exactly, which is why I would like to avoid it. The current profile
of the only account that matters on that machine contains some fragile
software, so I am not at all sure that if I reinstall and update
everything I will still have a working system.

Perhaps I could try to archive all the stuff in the profile, re-install
Guix, and recover my store items from the archive. But as far as I know
there is no way to install them into a profile afterwards.

BTW, I did find a way to run "guix pull" which has a good chance to work
on a more typical installation: remove $HOME/.config/guix and then run
"/usr/local/bin/guix pull". Unfortunately, this fails on my machine
because of insufficient disk space for building an enormous amount of
packages. Even gtk, although I am on a headless server.

I actually wonder if it is reasonable to run Guix on such a limited
machine. My store fills up 1/3 of the 10 GB partition, and that's right
after a "guix gc". Perhaps I should keep a profile with that machine's
software on my main Guix machine and just copy over the binaries from
time to time.

Konrad.

  reply	other threads:[~2018-11-14 15:21 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
2018-11-13 16:00         ` swedebugia
2018-11-14 15:21           ` Konrad Hinsen [this message]
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=m1a7mbznuo.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.