IRC channel logs
2026-06-04.log
back to list of logs
<mlxdy>It looks like problem with sudo is fixed. <stephen0>switchy solved the polkit/network manager issue and shared a snippet, perhaps they could be persuaded to share again <loquatdev>I'm working on a Guix image record to boot on a Raspberry Pi. Since the RPi firmware can boot the Linux kernel directly, is there a way I can specify no bootloader in the operating-system record? <loquatdev>I haven't really worked with Guix images before so this is new to me. <loquatdev>Basically I want to put the kernel, initramfs and some RPi specific files in the first partition and the store and userspace stuff in the second. Perhaps I should define my own bootloader object? <ieure>loquatdev, There's an example operating-system you can start from in gnu/system/examples/raspberry-pi-64.tmpl <ieure>I've been trying off and on to make a bootable image for my raspi, but I haven't been able to, there's either a system-image bug or I'm using it wrong. And I don't think I'm using it wrong. <apteryx>jlicht: I was wondering how are cycles typically handled for the npm-binary-importer? <apteryx>do you create some bootstrap variant, the usual fixup in Guix? <jlicht>apteryx: they are not, as of yet. <apteryx>ah yes, I mean if you encounter them after an import and want to fix it up; is there some common idiom you use? <jlicht>if you need that, I think the path of least resistance is adapting it to be a "lockfile importer" that uses npm to download deps and construct the 'correct' node_modules structure, so effectively you'd build packages with all their deps bundled, but AFAIK that hasn't really been done yet <jlicht>it would depend on the situation indeed :). Creating -bootstrap variants (perhaps by patching sources to disable functionality) could help, depending on circunstances <apteryx>I see, so it could become similar to what we do with Rust crates <apteryx>(if adapted to become a lockfile importer) <apteryx>one annoyance is that npm-binary-importer imports e.g. node-picocolors-1.1.1 while there is already a node-picocolors variable <apteryx>either it should be adapted to look for a non-version suffixed variable name, or we should leave the versions in the variables <apteryx>is semantic versioning common in the node community? <apteryx>on guix lint: guix/ui.scm:1030:18: In procedure #f: unspecified zlib error <apteryx>perhaps they changed their compressor <efraim>I've rebuilt rust-alsa-sys-0.3.1 to generate the alsa-lib bindings but our version of bindgen is too new (by several years...) so now it's causing build failures