bug#26901: During offload, in procedure send-files, '=' applied to #false
Any idea what went wrong with this aborted build? https://hydra.gnu.org/build/2043652 Nix error output: --8<---cut here---start->8--- these derivations will be built: /gnu/store/7myxmyy4q8jx8fqfz8y13vvynx31vf9m-spice-0.12.8.drv process 13271 acquired build slot '/var/guix/offload/hydra.gnunet.org/2' load on machine 'hydra.gnunet.org' is 6.25 (normalized: 1.5625) @ build-started /gnu/store/7myxmyy4q8jx8fqfz8y13vvynx31vf9m-spice-0.12.8.drv - x86_64-linux /var/log/guix/drvs/7m//yxmyy4q8jx8fqfz8y13vvynx31vf9m-spice-0.12.8.drv sending 3 store items to 'hydra.gnunet.org'... exporting path `/gnu/store/4q2vjqbi8h0im5fg9vy1ndwv9bixnw2s-spice-0.12.8-guile-builder' exporting path `/gnu/store/7myxmyy4q8jx8fqfz8y13vvynx31vf9m-spice-0.12.8.drv' Backtrace: In ice-9/boot-9.scm: 160: 14 [catch #t # ...] In unknown file: ?: 13 [apply-smob/1 #] In ice-9/boot-9.scm: 66: 12 [call-with-prompt prompt0 ...] In ice-9/eval.scm: 432: 11 [eval # #] In ice-9/boot-9.scm: 2404: 10 [save-module-excursion #] 4056: 9 [#] 1727: 8 [%start-stack load-stack #] 1732: 7 [#] In unknown file: ?: 6 [primitive-load "/gnu/store/v61l1zcf5ph0vvxajk3b0dqrmqbz495y-guix-0.11.0-8.8d12/bin/.guix-real"] In guix/ui.scm: 1222: 5 [run-guix-command offload "x86_64-linux" "3600" "1" "72000"] In guix/scripts/offload.scm: 753: 4 [guix-offload "x86_64-linux" "3600" "1" "72000"] In ice-9/boot-9.scm: 160: 3 [catch srfi-34 # ...] 160: 2 [catch system-error ...] In guix/scripts/offload.scm: 377: 1 [transfer-and-offload # # # ...] 470: 0 [send-files # #] guix/scripts/offload.scm:470:6: In procedure send-files: guix/scripts/offload.scm:470:6: In procedure =: Wrong type argument in position 1: #f @ hook-failed /gnu/store/7myxmyy4q8jx8fqfz8y13vvynx31vf9m-spice-0.12.8.drv - 256 builder for `/gnu/store/7myxmyy4q8jx8fqfz8y13vvynx31vf9m-spice-0.12.8.drv' failed with exit code 1 error: build of `/gnu/store/7myxmyy4q8jx8fqfz8y13vvynx31vf9m-spice-0.12.8.drv' failed --8<---cut here---end--->8---
bug#25852: Users not updating their installations of Guix
On 05/12/2017 at 10:29 Ludovic Courtès writes: > Ricardo Wurmus skribis: > >> Ludovic Courtès writes: >> >>> myglc2 skribis: >>> How about extending this ... > + (warning (G_ "Your Guix installation is getting old. Consider > +running 'guix pull' followed by '~a' to get up-to-date > +packages and security updates.\n") ... to inform the user how old the installation is? >>> >>> Good idea. I did that and pushed as >>> 7fd952e05203d975fcb6cdabd2f742ade1b31b66. >> >> Does this do the right thing when .config/guix/latest points at a git >> checkout? > > No it doesn’t, but I would argue that it unsupported. ;-) > >> The mtime of the “.config/guix/latest” link on one of my machines is >> from 2016, so Guix says it is too old, but it points to a git >> checkout, which is recent. > > I would suggest: > > export GUIX_DISTRO_AGE_WARNING=1000m > > as a workaround. WDYT? This alters guix's stock behavior if/when one switches back to using 'guix pull'. Maybe a better thing to do is the following each time you update guix from a git checkout ... ln -f -s -T ~/src/guix/ ~/.config/guix/latest sudo ln -f -s -T ~/src/guix/ /root/.config/guix/latest
bug#26897: ‘cmake-build-system’ does not support cross-compilation
Currently ‘cmake-build-system’ does not support cross-compilation, which is becoming more and more of a problem. For instance, it prevents cross-compilation of Guix: --8<---cut here---start->8--- $ guix build guix --target=aarch64-linux-gnu -n guix build: error: gnu/packages/ssh.scm:59:2: libssh-0.7.4: build system `cmake' does not support cross builds --8<---cut here---end--->8--- I think CMake supports cross-compilation in theory, so we should try to implement it. Ludo’.
bug#25852: Users not updating their installations of Guix
Ricardo Wurmus skribis: > Ludovic Courtès writes: > >> myglc2 skribis: >> >>> How about extending this ... >>> + (warning (G_ "Your Guix installation is getting old. Consider +running 'guix pull' followed by '~a' to get up-to-date +packages and security updates.\n") >>> >>> ... to inform the user how old the installation is? >> >> Good idea. I did that and pushed as >> 7fd952e05203d975fcb6cdabd2f742ade1b31b66. > > Does this do the right thing when .config/guix/latest points at a git > checkout? No it doesn’t, but I would argue that it unsupported. ;-) > The mtime of the “.config/guix/latest” link on one of my machines is > from 2016, so Guix says it is too old, but it points to a git > checkout, which is recent. I would suggest: export GUIX_DISTRO_AGE_WARNING=1000m as a workaround. WDYT? Thanks, Ludo’.