From: Julien Lepiller <julien@lepiller.eu>
To: Gottfried <gottfried@posteo.de>, help-guix@gnu.org
Subject: Re: bad use of syntactic keyword
Date: Sat, 11 Mar 2023 15:26:54 +0100 [thread overview]
Message-ID: <CB6ACA50-FCF6-4E99-B1EB-013E0B3568F0@lepiller.eu> (raw)
In-Reply-To: <23b707cf-7da8-073b-310e-21b5e6e30808@posteo.de>
Ah but the home-redshift-service-type is a home service, not a system service. It's meant to be used with guix home, not guix system.
Le 11 mars 2023 11:15:20 GMT+01:00, Gottfried <gottfried@posteo.de> a écrit :
>Hi,
>thanks for help
>
>I have now got:
>
>> (service home-redshift-service-type
>> (home-redshift-configuration
>> (location-provider 'manual)
>> (latitude 52.5) ;northern hemisphere
>> (longitude 13.5))) ;Berlin
>> (modify-services %desktop-services
>> (guix-service-type
>> config => (guix-configuration
>> (inherit config)
>> (extra-options (list "--gc-keep-derivations=yes" "--gc-keep-outputs=yes"))))
>> (sane-service-type _ => sane-backends)))))
>....................................................................................
>but running system reconfigure..
>I am getting now another message:
>
>> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
>> error: home-redshift-service-type: unbound variable
>.................................................................................
>I copied the "redshift-service-type" part
>from the manual into my config.scm
>so I don’t find the "unbound variable".
>
>Kind regards
>
>Gottfried
>
>
>
>Am 09.03.23 um 18:20 schrieb Julien Lepiller:
>> You have an extra closing parenthesis at the end of this line:
>>
>> (extra-options (list "--gc-keep-derivations=yes" "--gc-keep-outputs=yes")))))
>>
>> Remove one and adjust next lines if needed :)
>>
>
>>> %base-initrd-modules)))
>>>
>
>
next prev parent reply other threads:[~2023-03-11 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 16:49 bad use of syntactic keyword Gottfried
2023-03-09 17:20 ` Julien Lepiller
2023-03-11 10:15 ` Gottfried
2023-03-11 14:26 ` Julien Lepiller [this message]
2023-03-09 22:32 ` Marek Paśnikowski
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=CB6ACA50-FCF6-4E99-B1EB-013E0B3568F0@lepiller.eu \
--to=julien@lepiller.eu \
--cc=gottfried@posteo.de \
--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).