From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Lirzin Subject: Re: Unable to configure a system with 'cuirass-service' Date: Thu, 15 Dec 2016 22:58:30 +0100 Message-ID: <874m247t2x.fsf@gnu.org> References: <20161026130558.31924-1-mthl@gnu.org> <20161026130558.31924-3-mthl@gnu.org> <87k2ctkj7h.fsf@gnu.org> <87bmwy53kn.fsf@gnu.org> <87k2bk63eg.fsf@we.make.ritual.n0.is> <87y4007e6n.fsf@zancanaro.id.au> <87k2bj7rfj.fsf@we.make.ritual.n0.is> <87vav37qky.fsf@zancanaro.id.au> <87polbzst7.fsf@we.make.ritual.n0.is> <87twan7kdu.fsf@zancanaro.id.au> <87a8cf9z6s.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48355) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cHe2t-00011H-58 for guix-devel@gnu.org; Thu, 15 Dec 2016 16:58:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cHe2s-0000pk-A6 for guix-devel@gnu.org; Thu, 15 Dec 2016 16:58:35 -0500 In-Reply-To: <87a8cf9z6s.fsf@gnu.org> (Mathieu Lirzin's message of "Thu, 01 Dec 2016 21:22:51 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: ng0 Cc: guix-devel@gnu.org Hi, Mathieu Lirzin writes: > Carlo Zancanaro 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