From: ng0 <ngillmann@runbox.com>
To: Dmitry Nikolaev <cameltheman@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: Error in gexp.scm. Unrecognized keyword.
Date: Sat, 24 Sep 2016 21:25:31 +0000 [thread overview]
Message-ID: <8760pl2do4.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <CAH3JXcFsiR0W-SLgN7cC1+0gTsTOpE1dZeoF6omge+qUE_P9yg@mail.gmail.com>
Hi,
Dmitry Nikolaev <cameltheman@gmail.com> writes:
> Hi.
>
> I wanted to update my GuixSD installation, but everytime I run "guix system
> reconfigure ..." I'm getting
>
> guix/gexp.scm:314:0: In procedure computed-file:
> guix/gexp.scm:314:0: In procedure #<procedure computed-file (name gexp
> #:key options)>: Unrecognized keyword
>
> I've tried guix pull and guix refresh, nothing helped.
>
> What is wrong with my guix installation and gexp.scm? I haven't seen
> anybody complaining about it in this mailing list. What do I have to do to
> update my GuixSD installation?
>
> Dmitry Nikolaev
What is the exact command you are running?
The reconfigure needs to be passed the system config file, usually named
config.scm (as suggested by the documentation).
So when I update my systems I do:
guix system build /etc/config.scm; sudo guix system reconfigure /etc/config.scm
--
ng0
next prev parent reply other threads:[~2016-09-24 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 20:35 Error in gexp.scm. Unrecognized keyword Dmitry Nikolaev
2016-09-24 21:25 ` ng0 [this message]
2016-09-25 8:34 ` Alex Kost
2016-09-25 16:56 ` Leo Famulari
-- strict thread matches above, loose matches on Subject: below --
2016-09-28 9:06 Dmitry Nikolaev
2016-09-28 14:10 ` Alex Kost
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=8760pl2do4.fsf@we.make.ritual.n0.is \
--to=ngillmann@runbox.com \
--cc=cameltheman@gmail.com \
--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).