<ZillaThe4>my tty is being spammed with output from system services, such as ntpd. does anyone know how i can redirect that output?
<efraim>civodul: I'm testing them now by linting the refresh option of ~450 crates
<efraim>well, new plan, Throw to key `gnutls-error' with args `(#<gnutls-error-enum A TLS fatal alert has been received.> handshake)'.
<gnu_srs1>Hello again: I have now cross-built the bootstrap binaries for i586-pc-gnu. Should the *.xz or .tar out untarred files be installed in
<gnu_srs1>The built Hurd box at guix-1.0.1/gnu/packages/bootstrap?
<pinoaffe>civodul: well I packaged boost.python myself, and set it as a dependency of nextpnr, but the build scripts can't find it, so either my package is wrong or the build scripts are, and I have no clue how to find out which one it is
<efraim>civodul: guix/import/crate.scm:200:31: In procedure crate->guix-package:
<efraim>In procedure struct_vtable: Wrong type argument in position 1 (expecting struct): #f
<gnu_srs1>Looking at gnu/packages/bootstrap for other architectures have only the binary files: bash mkdir tar xz
<efraim>and after 'make clean && make clean-go' guix import: error: failed to download meta-data for package 'rust-blas-sys'
<gnu_srs1>Secondly how to make the built guix find them: ./pre-inst-env guix build hello? Or should *.drv files be created first??
<efraim>civodul: looked like I had a typo before, it's working great except for when I have a tls wrapping error
<rekado>gnu_srs1: the usual way to port Guix to other architectures is to edit the targets that download / unpack the generated bootstrap tarballs.
<rekado>gnu_srs1: I have an old patch here somewhere
<rekado>this hasn’t been done for the Hurd yet, presumably because we don’t offer official bootstrap binaries yet.
<rekado>(and I didn’t commit the patch because at least of my binaries segfaults on the Hurd)