all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: julien lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: How do I fix a messed-up Guix?
Date: Tue, 16 May 2017 16:47:24 +0200	[thread overview]
Message-ID: <20170516144724.GA9904@thebird.nl> (raw)
In-Reply-To: <38fe62eadaffe4f7823c81af2e1cc1ea@lepiller.eu>

If you still have guix in the store you can use the store path to
reach and run it.

As I had something similar today that there was no recent guix... I
actually restored with a slightly older 'guix pack' from a different
machine.

  https://www.gnu.org/software/guix/news/creating-bundles-with-guix-pack.html

You have to use an older version that does not get overwritten by a
new Guix. Otherwise the update will fail dramatically. It happened to
me first time :)

Alternatively you can unpack the store part of the binary install and
use that. Again, make sure you are not reinstalling the exact same
version.

If you still have a working guix you should use 'guix archive'.

Many options.

Pj.

On Tue, May 16, 2017 at 04:03:19PM +0200, julien lepiller wrote:
> Le 2017-05-16 15:11, Konrad Hinsen a ??crit??:
> >On 16/05/2017 15:02, Konrad Hinsen wrote:
> >
> >>I ended up rolling back until my profile no longer contained "guix" (I
> >>have no idea how I could ever produce such a profile), so now I am
> >>completely stuck. Any idea for getting out of this mess?

  reply	other threads:[~2017-05-16 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 13:02 How do I fix a messed-up Guix? Konrad Hinsen
2017-05-16 13:11 ` Konrad Hinsen
2017-05-16 14:03   ` julien lepiller
2017-05-16 14:47     ` Pjotr Prins [this message]
2017-05-16 15:21     ` 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=20170516144724.GA9904@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@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.