unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Lirzin <mthl@gnu.org>
To: ng0 <ng0@libertad.pw>
Cc: guix-devel@gnu.org
Subject: Re: Unable to configure a system with 'cuirass-service'
Date: Fri, 16 Dec 2016 00:15:06 +0100	[thread overview]
Message-ID: <87zijw6ayt.fsf@gnu.org> (raw)
In-Reply-To: <87h964by5u.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (ng0@libertad.pw's message of "Thu, 15 Dec 2016 22:55:09 +0000")

ng0 <ng0@libertad.pw> writes:

> Mathieu Lirzin <mthl@gnu.org> writes:
>
>> Hi,
>>
>> Mathieu Lirzin <mthl@gnu.org> writes:
>>
>>> Carlo Zancanaro <carlo@zancanaro.id.au> writes:
>>>
>>>> On Thu, Dec 01 2016, ng0 wrote 
>>>>> I tried that before (though I did just think it was wrong) and now I
>>>>> get the same message as yesterday:
>>>>>
>>>>> ...
>>>>>
>>>>> In gnu/services/cuirass.scm:   81: 1 [cuirass-shepherd-service #] In
>>>>> unknown file:    ?: 0 [string=? "" ((# # # # ...))]
>>>>>
>>>>> ERROR: In procedure string=?: ERROR: In procedure string=: Wrong
>>>>> type argument in position 2 (expecting string): (((#:name . "guix")
>>>>> (#:url . "git://git.savannah.gnu.org/guix.git") (#:load-path . ".")
>>>>> (#:file . "/.../cuirass/tests/gnu-system.scm") (#:proc . hydra-jobs)
>>>>> (#:arguments (subset . "hello")) (#:branch . "master")))
>>>>
>>>> It looks like cuirass is expecting the specifications to be a string,
>>>> not a list. I don't know anything about cuirass, so I can't help you
>>>> to configure the cuirass-service.
>>>>
>>>> Looking at the source, specifications has a comment ";string
>>>> (file-name)". It looks like the "specifications" field of the
>>>> configuration is just equivalent to the --specifications argument to the
>>>> cuirass command, if that helps at all.
>>>
>>> Indeed, this is a mistake on my side.  Here are 2 patches that should
>>> fix this issue.
>>
>> I went ahead and pushed them in commits:
>>
>>  - 44ccd9622eb4a0083d4f833a61172973390ca62b
>>  - 57aa94bd7e7d530e52356723c8f1dbf727144b25
>>
>> Thanks,
>>
>> -- 
>> Mathieu Lirzin
>>
>
> Thanks, I wasn't able to test them before and provide you with
> feedback, I was just busy and the CI is kind of low priority for
> gnunet. 

Sure no problem.

-- 
Mathieu Lirzin

      reply	other threads:[~2016-12-15 23:15 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       ` Unable to configure a system with 'cuirass-service' ng0
2016-11-30 23:14         ` 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 [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=87zijw6ayt.fsf@gnu.org \
    --to=mthl@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ng0@libertad.pw \
    /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).