Hi Clément,
>> I have a server running GuixSD with Cuirass and it’s supposed to build a >> bunch of user-provided manifests continuously. These manifests refer to >> packages that are defined in a separate repository that is on >> GUIX_PACKAGE_PATH, so really the Cuirass specification for them depends >> on two repositories. Can we express this with specifications? > > Yes, the Cuirass manual shows an example that does exactly what you > want: […] Beautiful! Thanks for pointing this out to me. >> Another problem is that Cuirass crashes on startup. The Cuirass log >> shows me this: >> >> --8<---------------cut here---------------start------------->8--- >> 2018-08-09T16:54:05 running Fibers on 4 kernel threads >> Uncaught exception in fiber ##f: >> In ice-9/eval.scm: >> 619:8 1 (_ #(#(#<directory (fibers) 127b500> #<<scheduler> ?> ?))) >> In unknown file: >> 0 (_ #<procedure 3de7aa0 at ice-9/eval.scm:330:13 ()> #<?> ?) >> ERROR: In procedure for-each: Wrong type argument: #f >> --8<---------------cut here---------------end--------------->8--- >> >> The Cuirass process remains, but appears to be stuck. > > This is because your specification list is invalid. I just noticed the > Guix manual about Cuirass is out of date. Please, have a look at the > Cuirass manual instead. Can we prevent this unhelpful error message by validating the specifications? -- Ricardo
