<cbaines>I've tried quite a few pids, with both /run/current-system/profile/bin/bash and /bin/sh, but nothing seems to work
<alezost>buenouanq: I think you can try "/etc/X11/xorg.conf.d/". BTW I'm pretty sure you are not supposed to modify "/usr/share/X11/xorg.conf.d" on Debian, as user configurations should go to /etc (I mean on classic distros; on GuixSD or NixOS you modify your system with a system config file)
<albertoefg>alezost: do you have a link where i can lear about that system config
<alezost>albertoefg: it's in the guix manual: (info "(guix) System Configuration")
<alezost>I think you can still use "/etc/X11/xorg.conf.d/", but the GuixSD way is to use 'xorg-configuration-file' as described at (info "(guix) X Window") ← this would probably be not easy to figure out
<ZombieChicken>I'm not 100% sure, but I think system reconfigure is the easier way to update the system, though I seem to recall you can use --profile to run guix package for the system profile
<rekado>I have a mu4e action to apply patches directly from the mu4e-view with "a g".
<ZombieChicken>civodul: I'm curious; any idea how much longer it will be before encrypted root is a thing?
<baconicsynergy>I'm reading about guix system reconfigure in the manual, and there's something I don't get. It says it won't upgrade a service that's currently running... but when I reboot, will it switch to the updated service?
<baconicsynergy>Will 'guix pull && guix system reconfigure --fallback asdf.scm' be a safe and sufficient operation?
<jmd>That's good. Whole root, or just parts of root?
<ng0>I like the endurance of the people packaging KDE, and also the one who is porting Guix to Hurd/Mach
<ng0>guix build: error: build failed: derivation `/gnu/store/2nhqr0kbfjcr8lfb0168dbdz110xf97c-openssl-1.1.0b.drv' may not be deterministic: output `/gnu/store/pdjyffqmxz0nxgw1xpy163yqwy5hdmww-openssl-1.1.0b' differs (guix build --check openssl) .. so why is openssl not deterministic? I found some open reproducible bugs, and some addressed in earlier versions of openssl already
***eric is now known as bavier`
<Apteryx>Hello! I'm trying to get doc-view mode to display PDFs in Emacs, and apparently I need to install Ghostscript (gs command). I've read the thread where ghostscript gs was spinned in another output, so now we have "ghostscript", "ghostscript-gs", "ghostscript-with-x" and "ghostscript-gs-with-x". Which one should I install? Would "ghostscript-gs" be OK, or do I need to explicitly use "ghost-scriptgs-with-x" if I'm
<Apteryx>I'm guessing the latter is what I need, but curious what would happen if I just install "ghostscript-gs" without the "with-x" suffix. Seems the only difference is the following added inputs for the "with-x" variant: libext and libxt.
<kablaam>hi, I'm trying to create a vm image for qemu. I'm running: guix pull & guix system vm-image config.scm --image-size=15G
<kablaam>and the system command fails with this message: output path `/gnu/store/a3zcv0b3x8gpvw5in2l1awncp7bjx9pm-geiser-0.9.tar.gz' should have sha256 hash `1n772ysl1dmn0vy3gk230ymyjm14h93zw99y6h2rqp1ixy7v43dm', instead has `0phz9d8wjk4p13vqannv0003fwh8qqrp0gfzcs2hgq1mrmv1srss'
<ZombieChicken>Well, if a feature is likely to break in some cases (and the more people use Guix(SD), the more likely something will break somewhere), it can cause users problems that aren't trivial to fix
<ZombieChicken>Roll-back is nice and all, but it's a bit of a pain if what breaks is the roll-back system
<lfam>This is how Guix offers an improvement on the old mutated /usr model
<lfam>I can update, for example, OpenSSL for some packages and not for others, and all my packages will keep working properly
<lfam>They will each continue to refer to the correct and separate dependency graphs
<lfam>And I think that "stable" branches cause too many problems for upstream projects, pushing them to lame "solutions" like flatpak et al. But, stable branches are necessary for the old distros, because it's impossible for them to offer working systems otherwise.
<ng0>"global" use cases would be good. like an --with-input=openssl=libressl , only in the system config. (and enjoy fixing what's not yet compatible)
<lfam>I think that the functional package management system (Guix / Nix) cut the Gordian knot