From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, ison <ison@airmail.cc>,
Divan Santana <divan@santanas.co.za>
Subject: Re: Noob issues with maintaining a guix laptop system
Date: Tue, 04 Jun 2019 09:11:57 +0200 [thread overview]
Message-ID: <B62308BF-C4B8-41F8-8A51-A0E4E2B2933D@lepiller.eu> (raw)
In-Reply-To: <20190604061710.nwkbw6uqxyhwhayh@cf0>
Le 4 juin 2019 08:17:11 GMT+02:00, ison <ison@airmail.cc> a écrit :
>Just to be clear, when a reconfigure fails you can make any necessary
>changes
>and run it again. Guix operations are atomic so it doesn't actually
>change the
>state of your system in any way until it finishes.
>
>But, if you're asking about rolling back the "guix pull" so that you
>can run
>reconfigure with the older versions as if you had never ran "guix pull"
>in the
>first place, then I think you could try this:
>guix describe
>which should print out the "commit" used when you last reconfigured the
>system.
>Then you could try the following command with <commit-string> replaced
>with the
>value you got above:
>guix pull --commit=<commit-string>
>That should make sure your package data matches what was used last time
>you
>successfully reconfigured.
That's a good suggestion, except guix describe will tell you the connit of the currently installed guix, which is the one you've guix pull'ed to.
I thenk you can use guix package to manage the guix pull profile, like so:
guix package -p /var/guix/profiles/per-user/current-guix --list-generations
You can also use --roll-back or switch directly to an older generation.
But in general I think it would be better for you to report your failure(s) so we can help and fix them :)
>
>As for the swapfile, it should work exactly how you showed.
>That error makes me think the problem is with how you set up the
>swapfile. Did
>you run "dd" to allocate space for the swapfile?
And run mkswap on it?
next prev parent reply other threads:[~2019-06-04 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 14:44 Noob issues with maintaining a guix laptop system Divan Santana
2019-06-04 6:17 ` ison
2019-06-04 7:11 ` Julien Lepiller [this message]
2019-06-05 18:27 ` Divan Santana
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B62308BF-C4B8-41F8-8A51-A0E4E2B2933D@lepiller.eu \
--to=julien@lepiller.eu \
--cc=divan@santanas.co.za \
--cc=help-guix@gnu.org \
--cc=ison@airmail.cc \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).