unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Dustin <oury.dustin@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: GuixSD cannot initialize system config
Date: Sun, 24 Dec 2017 18:17:49 +0000	[thread overview]
Message-ID: <877etct2gi.fsf@cbaines.net> (raw)
In-Reply-To: <E536C05B-F2C8-4C47-89C1-60122A5D8465@posteo.de>

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]


Dustin <oury.dustin@posteo.de> writes:

> When I run the command #guix-system init /mnt/etc/my-os-config.scm /mnt where /mnt is the path I want to install the system on, it complained about some .scm file or something to do with #f. I don't really remember.

It would be useful to know the exact error message, and to see your
configuration file if possible. You can connect to the installer over
SSH from another machine if that makes copying the error and config file
easier.

> I did a little reading and it seems the solution is to upgrade the guix daemon, but how do I upgrade the guix daemon on a liveUSB?

That seems a bit odd, as the guix-daemon is usually quite separate, and
doesn't often cause problems.

Upgrading might be possible, but if you wanted to do this, I think it
would be easier to generate [1] a updated installation image with the
newer version of the guix package on it. But first, it would be good to
check the error message and your configuration file.

1: https://www.gnu.org/software/guix/manual/html_node/Building-the-Installation-Image.html#Building-the-Installation-Image

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

      reply	other threads:[~2017-12-24 18:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-24 14:28 GuixSD cannot initialize system config Dustin
2017-12-24 18:17 ` Christopher Baines [this message]

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=877etct2gi.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=help-guix@gnu.org \
    --cc=oury.dustin@posteo.de \
    /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).