I am trying to get a "#guix pull" to work on my orangepirv2 and hitting a known issue with findutils-boot0 hanging on test_rw. So, I am now installing #debian 13 on riscv #qemu to see if I can get around that bug and provide substitutions for the orangepirv2

@craigbro There is already a merge request available for your issue:
https://codeberg.org/guix/guix/pulls/1207

It's only affecting *old* installations (e.g., the official 1.4 release binaries) and riscv64 SoCs with >= 8 cores. It's already fixed in newer `gnulib` releases, but the way how #guix works, perfectly reproduces this historic bug as well.

gnu: Modify `gnulib-tests/test-lock.c` to prevent failures and crashes on riscv64

Modify `gnulib-tests/test-lock.c` to prevent failures and crashes on riscv64. It only disables the execution of `rwlock` tests of `test-lock`, one of the `gnulib-tests`, for the `riscv64` platform. Fixes: #1161 These modifications alter the build check phase of: - findutils - libunistring...

Codeberg.org
@mash_graz Thanks for the heads up. I think I have a solution past this issue. I cross-compiled a guix-binary tarball on another system,
@mash_graz @craigbro How hard is it to run 'guix build ...' every so often and plonk the binary on GIT? Does there need to be a formal release cycle for this to happen?