"Tanguy Le Carrour" <[email protected]> skribis: >>> while setting up the child process: in phase exec: executing >>> `/gnu/store/rv7ym20nf7dkv81rr6f0pr2mv6ww7dx1-guile-3.0.9/bin/guile': >>> No such file or directory
[...] > (machine-ssh-configuration > (host-name "asura.lan") > (host-key "ssh-ed25519 AAAA[…]") > (system "armhf-linux") And: --8<---------------cut here---------------start------------->8--- $ file /gnu/store/rv7ym20nf7dkv81rr6f0pr2mv6ww7dx1-guile-3.0.9/bin/guile /gnu/store/rv7ym20nf7dkv81rr6f0pr2mv6ww7dx1-guile-3.0.9/bin/guile: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /gnu/store/5rbyi78lfdg126d0xgsx47aq60kfrxn7-glibc-2.41/lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0, stripped --8<---------------cut here---------------end--------------->8--- So this is all good… assuming /gnu/store/2i1pqnkah9jmqlsilxpg0zmfm0wzqq4h-remote-assertion.scm.drv was actually built on asura.lan. Could you try “guix build /gnu/store/2i1pqnkah9jmqlsilxpg0zmfm0wzqq4h-remote-assertion.scm.drv” on asura.lan? I vaguely remember a bug where you have to specify: (build-locally? #f) in your ‘machine-ssh-configuration’ when the machine you’re deploying to has a different architecture than the one running ‘guix deploy’. Maybe this is evidence that the bug still exists… Ludo’.
