From: Alex Kost <alezost@gmail.com>
To: Dmitry Nikolaev <cameltheman@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Error in gexp.scm. Unrecognized keyword.
Date: Wed, 28 Sep 2016 17:10:28 +0300 [thread overview]
Message-ID: <87d1jof73f.fsf@gmail.com> (raw)
In-Reply-To: <CAH3JXcFqvikD7=rpTdeq-OQ22yfB3H-wezYv2XJNPeEYw118iw@mail.gmail.com> (Dmitry Nikolaev's message of "Wed, 28 Sep 2016 12:06:59 +0300")
Dmitry Nikolaev (2016-09-28 12:06 +0300) wrote:
>
> > 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?
>
> Most likely there is some problem with your OS configuration
> (typically
> '/etc/config.scm'). Can you share it if there is nothing
> sensitive or
> private in it?
>
>
> Looks like something is wrong in my xorg-ati.scm module.
>
> I'm using non-libre linux with free drivers for Radeon with blob in
> kernel and some additional configuration for it.
>
> My entire configuration is open and located on github
>
> https://github.com/8p8c/my-guix
>
> You can find my config.scm there
>
> https://github.com/8p8c/my-guix/blob/master/config.scm
>
> As my xorg-ati.scm
>
> https://github.com/8p8c/my-guix/blob/master/packages/xorg-ati.scm
This file looks like you copied its contents from (gnu services xorg)
some time ago. I think the problem is that this code is already old
enough to conflict with the current guix code.
Such copying of some part of the guix code and using it in a system
config instead of the current guix code is not a right approach IMO. If
you think there is something that can't be configured by a user, please
report. But is using #:extra-config for 'xorg-configuration-file'
procedure not enough for you needs?
--
Alex
next prev parent reply other threads:[~2016-09-28 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 9:06 Error in gexp.scm. Unrecognized keyword Dmitry Nikolaev
2016-09-28 14:10 ` Alex Kost [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-24 20:35 Dmitry Nikolaev
2016-09-24 21:25 ` ng0
2016-09-25 8:34 ` Alex Kost
2016-09-25 16:56 ` Leo Famulari
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=87d1jof73f.fsf@gmail.com \
--to=alezost@gmail.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).