<acrow>Has anyone successfully completed the 'check' phase when building chez-scheme-for-racket-9.9.9-pre-release.16.drv? It seems to be a required portion of an up to date install of racket-minimal as well as racket. No issues seem to be opened on this...
<nckx>Oh, somebody else did. Are you sure you're on master, ChocolettePalett.
<distopico>nckx: I have an Asus KGPE-D16, it doesn't have nvme, so I'm using an pcie, but is not detected before the boot, and I want to have the root in the nvme for performance reasons, so I have the boot in the ssd that is detected and all the root in nvme, not sure if this is a common case, maybe mostly for old motheboard
<ChocolettePalett>Oh, I haven't tried building it lately, just wanted to make sure it wasn't my system's fault. Thank you very much for fixing it! Will try to build it now.
<nckx>distopico: Thanks for the answer! I can't wait to get rid of mine, it feels anachronistic (I had one in the 90s, because my 1.1 gig hard drive confused the BIOS). Maybe they are still more common than I think & I'm just lucky.
<rekado>yet when I deploy it builds stuff locally anyway: while setting up the build environment: a `aarch64-linux' is required to build `/gnu/store/djdpd9d4gbhv8kwqimw9faadg6hkapyb-gitile-0.1.4.drv', but I am a `x86_64-linux'
<rekado>nbconvert runs xelatex, but xelatex complains that “I can't find the format file `xelatex.fmt'”
<rekado>I just upgraded my own home profile, and yes: xelatex no longer works
<mfg[m]>i guess the inputs have to be changed, so do you have texlive-scheme-basic and texlive-collection-basic in that profile? those seem to be important (i only used luatex with the new packages, so not sure what you also need for xelatex)
<mfg[m]>guix shell texlive-collection-luatex texlive-collection-basic texlive-latexmk texlive-scheme-basic gives me a usable luatex
<rekado>I’ll add texlive-latex-base and see if that fixes it
<irfus>somehow store items related to grub configuration have got messed up along with a bunch of other stuff. `guix gc --verify=..` fixed most of them but errored on the grub items. Now system reconfigures are failing because of this.
<irfus>'gc --delete' doesn't work on those paths because they are still alive. Anything else I can try?
<jpoiret>if they're alive they probably can't be repaired, right
<jpoiret>janneke: I don't think this is doable on such a large scale though
<jpoiret>(finding tests that are failing on the Hurd)
<jpoiret>commendable effort but this is going to be a lot of work if we also want those tests to actually work
<jpoiret>irfus: you could rollback if you can and repair
<Zambyte>Hi, can anyone confirm if they received an email on help-guix with the subject "Using NoiseTorch with Sway and Polkit" yesterday? It seems like it sent on my end but I'm not seeing it in the archives
<Zambyte>Want to double check before trying to send it again
<RavenJoad>Does anyone here use msmtpq to queue email messages? I have been having problems, and want to double-check if someone else has solved it. If you do not use msmtpq, what do you use to queue mails for later sending instead?
<lambdanil>hi, is there a straightforward way to get firewall on Guix?
<lambdanil>I looked around if there's some Firewall service but didn't find anything
<msavoritias>because the commend "different services" in the description is confusing
<ngz>rekado: Hi! I fixed `python-nbconvert'. However, its propagated packages are wrong. `texlive-updmap.cfg' should only be used as a native inputs, since propagated inputs benefit from the profile build process. I understand (cf. our discussion about python-sphinx) that some texlive packages are expected as propagated inputs, but those only needed for the tests should be moved as native-inputs, wrapped in a texlive-updmap.cfg call. Do you
<ngz>rekado: another option is to keep them all as propagated inputs, along with texlive-collection-basic to get a standalone texmf tree. I don't think updmap.cfg is needed with XeTeX/XeLaTeX anyway.
<ngz>rekado: Confirmed. It is possible to remove `texlive-updmap.cfg' altogether, and list all texlive packages (those outside texlive-updmap.cfg and those inside), along with `texlive-collection-basic', as propagated inputs. Shall I just push this?
<lispmacs[work]>in my system scm file, if I have a service like (service tor-service-type), how do I modify that to pass shepherd options, like to not start the service and to have it disabled?