From: ng0 <ng0@libertad.pw>
To: guix-devel@gnu.org
Subject: Unable to configure a system with 'cuirass-service'
Date: Wed, 30 Nov 2016 21:53:11 +0000 [thread overview]
Message-ID: <87k2bk63eg.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87bmwy53kn.fsf@gnu.org>
Mathieu Lirzin <mthl@gnu.org> writes:
> Pushed in commit a7cf4eb6d99838606d8ecfa776f7e4920dfbb7f5 with bug fixed
> and requested changes.
>
> Thanks.
To begin to test the service, I tried this with this[0] system
config today and failed. I tried some variations, moving around
the let, checking for typos, let* instead of let, etc, but I
wasn't succesful.
What does this mean? I am able to configure the system with this,
but finally (cuirass-service) is silently ignored and never makes
it into the new system.
Is there anything obvious I have to change?
[0]: https://ptpb.pw/lIwS.scm
next prev parent reply other threads:[~2016-11-30 21:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 13:05 [PATCH 0/2] Cuirass package + service Mathieu Lirzin
2016-10-26 13:05 ` [PATCH 1/2] gnu: Add Cuirass Mathieu Lirzin
2016-10-26 13:36 ` David Craven
2016-11-29 22:25 ` Mathieu Lirzin
2016-11-30 13:10 ` Ludovic Courtès
2016-10-26 13:05 ` [PATCH 2/2] services: Add 'cuirass-service' Mathieu Lirzin
2016-10-26 13:35 ` David Craven
2016-10-26 14:42 ` Mathieu Lirzin
2016-10-26 18:57 ` David Craven
2016-10-27 0:22 ` Leo Famulari
2016-11-06 13:16 ` Andreas Enge
2016-10-27 13:36 ` Ludovic Courtès
2016-11-29 22:22 ` Mathieu Lirzin
2016-11-30 21:53 ` ng0 [this message]
2016-11-30 23:14 ` Unable to configure a system with 'cuirass-service' Carlo Zancanaro
2016-12-01 12:41 ` ng0
2016-12-01 12:59 ` Carlo Zancanaro
2016-12-01 13:23 ` ng0
2016-12-01 15:13 ` Carlo Zancanaro
2016-12-01 20:22 ` Mathieu Lirzin
2016-12-15 21:58 ` Mathieu Lirzin
2016-12-15 22:55 ` ng0
2016-12-15 23:15 ` Mathieu Lirzin
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=87k2bk63eg.fsf@we.make.ritual.n0.is \
--to=ng0@libertad.pw \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).