Ludovic Courtès skribis: > Hi Guillaume, > > Guillaume Le Vaillant skribis: > >> Currently no substitutes are built for the testing branch because the >> evaluation fails. The log at https://ci.guix.gnu.org/eval/16794/log/raw >> ends with: > > You mean the ‘staging’ branch? > Yes, I meant 'staging'. I often type 'testing' instead of 'staging', probably that pesky muscle memory!. >> guix/inferior.scm:247:2: ERROR: >> 1. &inferior-exception: >> arguments: (keyword-argument-error #f "Unrecognized keyword" () (#:builder)) >> inferior: #< pid: pipe socket: # close: # version: (0 1 1) packages: #> table: #>> >> stack: ((#f ("ice-9/boot-9.scm" 1763 13)) (raise-exception ("ice-9/boot-9.scm" 1666 16)) (raise-exception ("ice-9/boot-9.scm" 1668 16)) (#f ("guix/build-system/asdf.scm" 279 2)) (thunk ("guix/packages.scm" 1397 22)) (package-derivation ("guix/packages.scm" 1079 16)) (job ("gnu/ci.scm" 383 24)) (filter-map ("srfi/srfi-1.scm" 690 23)) (#f ("gnu/ci.scm" 497 31)) (map1 ("srfi/srfi-1.scm" 585 17)) (append-map ("srfi/srfi-1.scm" 672 15)) (hydra-jobs ("gnu/ci.scm" 482 4)) (#f ("ice-9/eval.scm" 158 9)) (#f ("ice-9/eval.scm" 158 9)) (with-exception-handler ("ice-9/boot-9.scm" 1735 10)) (call-with-prompt ("ice-9/boot-9.scm" 717 2)) (dynamic-wind ("ice-9/boot-9.scm" 141 2)) (#f (#f #f #f)) (#f ("guix/repl.scm" 92 21)) (with-exception-handler ("ice-9/boot-9.scm" 1735 10)) (with-exception-handler ("ice-9/boot-9.scm" 1730 15)) (#f ("guix/repl.scm" 119 7))) >> >> If I understand this correctly, there's a '#:builder' keyword somewhere >> that is causing a problem. Does someone know where it can come from, or >> how to fix the issue? > > Right. I’d look at guix/build-system/asdf.scm:279:2 on that branch (per > the inferior stack trace above). Does that give useful info? I didn't see any obvious problem in that file; the strange thing is that 'make', 'make as-derivation' and './pre-inst-env guix build ...' all work fine. In a local branch I merged the current master (3699ed6) into staging (de96ed1) and I'm going to try to start a local cuirass daemon to see wether I can reproduce the issue or not. Given that merging master in staging hasn't been done in a while, should I also push my updated staging branch, or maybe someone is already working on it?