Hey! > Mathieu, could it have to do with the fact that the manifest is within > the ‘guix’ channel? Using the attached little reproducer, I get a more interesting backtrace: --8<---------------cut here---------------start------------->8--- Backtrace: In ice-9/boot-9.scm: 1752:10 11 (with-exception-handler _ _ #:unwind? _ # _) In unknown file: 10 (apply-smob/0 #) In ice-9/boot-9.scm: 724:2 9 (call-with-prompt _ _ #) In ice-9/eval.scm: 619:8 8 (_ #(#(#))) In ice-9/boot-9.scm: 2835:4 7 (save-module-excursion _) 4380:12 6 (_) In gnu/ci.scm: 496:4 5 (cuirass-jobs _ _) In srfi/srfi-1.scm: 673:15 4 (append-map _ _ . _) 586:17 3 (map1 (list "x86_64-linux")) 586:17 2 (map1 (# …)) In gnu/ci.scm: 575:38 1 (_ #) In guix/packages.scm: 441:0 0 (%package-name-procedure #) guix/packages.scm:441:0: In procedure %package-name-procedure: In procedure package-name: Wrong type argument: # () 7f84f252ec00> --8<---------------cut here---------------end--------------->8--- The issue is that (gnu ci) expects manifests of packages and not manifests of origins. Hence, the "job-name" procedure that calls "package-name" on an origin fails. We could maybe generalize the manifests->packages to support packages and origins. The package-job procedure would also need some adjustment to call origin->derivation instead of package-derivation. WDYT? Thanks, Mathieu