unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ison <ison@airmail.cc>
To: Divan Santana <divan@santanas.co.za>
Cc: help-guix@gnu.org
Subject: Re: Noob issues with maintaining a guix laptop system
Date: Tue, 4 Jun 2019 00:17:11 -0600	[thread overview]
Message-ID: <20190604061710.nwkbw6uqxyhwhayh@cf0> (raw)
In-Reply-To: <87r28ak9tn.fsf@santanas.co.za>

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.

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?

  reply	other threads:[~2019-06-04  6:17 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 [this message]
2019-06-04  7:11   ` Julien Lepiller
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=20190604061710.nwkbw6uqxyhwhayh@cf0 \
    --to=ison@airmail.cc \
    --cc=divan@santanas.co.za \
    --cc=help-guix@gnu.org \
    /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).