<apteryx>question: why do we need --root in the 'boot-system' procedure (gnu build linux-boot), to specify the root mount devices, if we are already passing a list of <file-system> records as its MOUNTS argument? (which, I believe, should include the root file-system record). It seems redundant.
<apteryx>I guess it's nice that you can try booting a system from multiple devices at the Grub command line
<g_bor>Anyone knows what timezone the blog post dates should be in?
<truby>if I build with a gcc from guix I get warnings from glibc headers, I guess they aren't being marked correctly as system headers? It causes our code to fail to build because we build with -Werror :(
<civodul>g_bor: it's unspecified, but it happens to be CEST or CET most of the time :-)
<civodul>truby: yeah, that's on core-updates, right?
<nckx>It's only for humans anyway. Proggies have no legitimate reason to parse kernel configuration.
<bricewge>I'm willing to write it it, but I'm not sure in which section of the manual to put it.
<nckx>‘Kernel configuration’, which doesn't exist, because everyone seems to agree that the current MAKE-LINUX-LIBRE is suboptimal and should be replaced with… something. Or maybe that it doesn't belong in the manual at all. It's currently in doc/guix-cookbook.texi on the wip-cookbook branch.
<nckx>The manual focuses on processes: installing Guix System and configuring it declaratively. There's no ‘tour of your System as it actually exists on disc’ section AFAICS.
<bricewge>If it's in the cookbook it's good engouth for me then.
<nckx>s/processes/initial installation and Scheme abstractions/
<shrdlu68>I'm close to giving up at this point, I just don't know how to introspect the system.
<nckx>By inconsistency I didn't mean that some modules use _ and others -. Some use both depending on how you're asking. I think. Used to, anyway.
***MinceR_ is now known as MinceR
<roptat>shrdlu68, actually, guix is happy with virtio-pci, it installs the file, but at load time, it tries to load virtio-pic.ko which doesn't exist (probably, you have virtio_pci.ko installed though)
<Minall`>After doing a guix pull and tried to do a reconfigure, I had to shutdown my machine, my question is... Do I have to make another guix pull after reconfigure?
<quiliro>No you don't unless you want to upgrade the guix package (and the package list) fer the current user.
<apteryx>guix system reconfigure is always used locally, right? I mean, what does 'guix deploy' does (I haven't kept up to date with it, sorry) -- send the config.scm to the remote than reconfigure it there?
<grumbel>Anybody here using Guix on multiple monitors? I am currently trying to switch from the Ubuntu Xfce to the Guix Xfce, but when I maximize a window it gets stretched over all the monitors, instead of the current one
<grumbel>Feels like there is a libXrandr dependency not getting compiled in at some point
<bavier>grumbel: I use multiple monitors with guix's ratpoison, and things work fine. idk about xfce.
<Minall>bavier: Can you help me with my reconfigure problem, I'm trying to create an etc file
<agohoth>any light weight but non tiling madness wm?
<grumbel>problem might be in gtk+, as I am getting no match on "objdump -p /gnu/store/jr6kyk1qqhyb9wxxy7g0fp3k4yyi3rgn-gtk+-3.24.10/lib/libgdk-3.so.0 | grep -i xrandr", but trying same on the ubuntu libs gives a libXrandr reference
<grumbel>bavier: Trying to view the gtk+ build log and than maybe patching and rebuilding gtk+
<reepca>huh, yeah, that's weird. --no-substitutes seems to either cause repeat builds or changes the order of builds
<bavier>grumbel: 'guix build' has a '--log-file' option, which is maybe what you're looking for
<bavier>it has the unfortunate tendency of pointing to a log with "grafting ..." messages. In that case you probably want to include '--no-substitutes'
<bavier>but with that, my 'guix build --no-substitutes --log-file gtk+' seems to insist on building openssl. :/
<reepca>for example: 'guix build --dry-run --no-substitutes --check git' says The following derivation would be built: /gnu/store/na46y0k24d3pf50fvs70p9fmnzixvyxh-git-2.23.0.drv, but running it without --dry-run, it immediately starts building openssl
<bavier>oh, order of options seems to make a difference: "guix build --log-file --no-substitutes gtk+'
<mbakke>bavier: to get the actual build log, you need --no-grafts too
<mbakke>also, that would prevent pulling in openssl etc
<bavier>mbakke: ah, right :) to many things going at once
<grumbel>That however still leaves me with "guix build: error: no build log for '/gnu/store/f35d2zi13hvkwzxkmbb552nzll0pvz51-gtk+-3.24.10'", since I haven't build gtk+ on my machine I guess