<rekado_>pkill9: the name “GuixSD” was always an uneasy compromise. It also emphasized a difference between different uses of Guix that we found to complicate things more than it helped.
<rekado_>When it became obvious that the use of Guix for building VMs and container images is really not all that different from using Guix as a system on real hardware, adopting the new name was an almost obvious next step.
<rekado_>“Guix System” is what the “guix system” command produces – no matter if that’s a VM, a container image, or a “bare metal” operating system installation.
<rekado_>the similarities are more important than the differences
<vagrantc>so, symlinks aren't working out too well ... lrwxrwxrwx 2 root root 9 Dec 31 1969 /gnu/store/zn0862lzl2mr8zwwbhdhv7jgdpm3w9gk-bash -> /bin/bash
<vagrantc>which doesn't pull the system's /bin/bash into the build environment
<vagrantc>maybe that's why none of the substitutes are considered valid
<vagrantc>that was with "guix build hello --no-build-hook" ... without that still getting the issues where it can't find offload
<matt`>I'm considering switching to using Guix as my main distro and am trying to wrap my head around how I might deal with system configurations that aren't supported without patching guix itself. Is there a way to tell the system configuration to write an arbitrary file? For instance, let's say I needed a certain fstab file. When writing config.scm can I specify just arbitrary text that should go in /etc/fstab and have guix system do that
<matt`>similarly, is there an easy way to see how certain system configurations lead to the resulting changes in /etc files or other configuration files?
***MinceR_ is now known as MinceR
<reepca`>hm, despite the shepherd manual stating that list-actions has a default implementation for any service, doing, for example, "sudo herd list-actions udev" just gives "herd: service 'udev' does not have an action 'list-actions'"
<reepca`>looking through the code I've noticed that "sudo herd doc udev list-actions" does the desired job
<mouldysammich>hey all, how come gnome is still at 3.28? are there problems with newer versions?
<reepca`>civodul: I noticed that "sudo herd list-actions <some-service>" doesn't work (the manual mentions it as an action implemented by Shepherd itself), but "sudo herd doc <some-service> list-actions" does (gleaned from the sources). Is that a bug?
<vagrantc>how would guix know the hashes of the binaries? could i download them with guix download (or something similar) ?
<rekado>the hashes are recorded in gnu/packages/bootstrap.scm IIRC
<jonsger>vagrantc: guile-gcrypt needs libgrypt-devel, guile-git needs libgit2-devel, guile-newt needs newt-devel, guile-parted needs parted-devel, guile-sqlite needs sqlite3-devel. The packages are named slightly different on debian...
<krafter>civodul: Yes, the VM itself start fine, but it can't find the hard drive. I use the command in the link you sent me as a template, replacing the file part with the image created by guix system vm-image.
<civodul>so the initrd fails to find the root file system?
<dongcarl>Hey all, wondering what you guys do when a package is distributed with a Makefile.in and a Makefile.am, and you need to patch something in Makefile.am... Do you 1. Delete the Makefile.in, modify .am and regenerate?, or 2. Patch just Makefile.in, or 3. Patch both?
<rekado>kmicu: I never really considered an nvidia card because of how hostile they are, but I’m worried about how this amdgpu stuff could make it less likely that AMD cards can be used with free software alone.
<rekado>I got one old nvidia card from an institute workstation and it works fine, but it’s just as bad as the internal GPU on this ancient motherboard.
<kmicu>dongcarl: I used PRIME offloading on (liberated aka no firmware blobs) NixOS so I assume that should also work on Guix System (but not tested PRIME here yet).
<vagrantc>if a project isn't updating pypi.org ... is it ok to switch to git tags to update the version? the git tags are also signed with a trust path as an added benifit, unlike pypi.org packages... but looses guix refresh-ability
<kmicu>rekado: nVidia has that thing with ‘Use our signed firmware images to unlock performance’ otherwise they have perfomance close to Intel’s integrated GPUs. I recommend asking Mesa folks about libre OpenCL cards. Maybe Panfrost driver and Mali GPUs could be good for OpenCL today 🤷
<vagrantc>eats up a lot more disk space, obviously.
<vagrantc>but guix has never really been too afraid of that :)
<vagrantc>kkebreau: it's definitely been a while since i installed it
<kkebreau>Marlin1113: I would say that `patchelf --set-interpreter $(guix build -S glibc)/lib/ld-2.28.so [program]` is the quickest way to begin work with patchelf, but $(guix build glibc) gives three different folders...
<kkebreau>Whoops, there shouldn't be a "-S" in that command.