<oriansj>vagrantc: well greetd user account can be granted a sudo for shutdown/reboot and users who are physically at the computer can use it to shutdown/reboot but those who ssh in don't need that ability
<oriansj>although i do admit, if one were to write a greetd client and have it cause the greetd user account to shutdown the machine via ssh; it would be possible and I'd probably have to figure out a solution to that.
*vagrantc suspects ci.guix.gnu.org and bordeaux.guix.gnu.org are building with different locales ... speculating C vs. en_US.UTF-8
<vagrantc>well, this is new guix build: error: derivation `/gnu/store/infq1xs3czafcp97sx847ygg2ahnq168-libccd-2.1.drv' may not be deterministic: output `/gnu/store/anb18pcx7mfbz5h7q041k48m6vv4ay9n-libccd-2.1' differs
<devmsv>shcv[m]: there were just 4 URLs needed so I put them on /etc/hosts. I don't know if copying resolved.conf would have worked since it had name server configured
<psy0>Hello! Hopefully quick question. I'm having trouble googling what this syntax means in Guile: #'(stuff)
<sneek>ml_2, antipode says: I don't know if you can do that in the REPL, but in Guile programs, you can use 'continuable exceptions' to do things like that (try raise-continuable+with-exception-handler), and remember to _not_ use catch which doesn't preserve continuability)
<apteryx>unless that causes issues, to avoid exploding the dependency graph
<SamIaM>How to start dwm after guix install dwm? :D
<elais[m]>You have to create a desktop file to start it from the display manager otherwise you need to use an old fashioned startx script. If you use lxqt you can declare it as your WM
<jbv1[m]>Hello guix ! What is file-name supposed to do when using (method git-fetch) ? I thought it would cause the source to be checked out in a named subdirectory but that does not seem to be the case (I get "source" as directory name)
<lilyp>jbv1[m]: (file-name (git-file-name name version)) makes it so that the store item is /gnu/store/hash-mypackage-1.2.3 rather than /gnu/store/hash-git-checkout
<jbv1[m]>aaah ok so nothing to do with were it gets copied afterwards
<antipode>sneek: later tell nckx: (or anyone else with appropriate access to ci.guix.gnu.org): the antioxidant channel now targets core-updates, the specification at ci.guix.gnu.org needs to be changed.
<f1refly>when using guix offload, is there a way to handle machines becoming unavailable?
<f1refly>I configured my laptop to use my desktop computer for offloading, but my desktop computer is not alway turned on and now guix on my laptop seems to be stuck waiting for the offload machine to appear on the network
<f1refly>well, it's not exactly stuck, it fails to resolve the hostname and doesn't seem to get tired of doing that in a lopp
<antipode>I've pushed a commit that adds the rust to the manifest, hopefully that's sufficient to avoid it happening again.
<f1refly>I have another question. I want to include a local file containing udev rules in my system configuration. using plain-file I can make guix copy the file to the store and return the store location, which current will be written to the udev file: https://paste.rs/s9w.scm
<antipode>On the plus side, people with access to the various hydra-guix-... now could go wild with "guix challenge".
<f1refly>how can i make it so that guix will make the udev file a link to the file in the store?
<antipode>Looking at udev-rules in (guix)Base services, udev-rule does not accept separate files.
<antipode>It wants the contents of the file instead.
<jbv1[m]>another reason to do this is that right now your julia package definition only works on realased tarballs, you cannot use it on a git checkout. And that would be interesting to be able to run it on a git checkout to find out which commit made the package definition obsolete
<jbv1[m]>also using a tarball as a source which bundles other tarballs in it that does not feel very nice to me
<vagrantc>julia fails to buidl reproducibly, and i've not yet managed to get diffoscope to finish a build (some run for over 24 hours)
<superkamiguru>Hope I am not interrupting any other conversations, but does anyone have experience setting up a 9p file-system?
<superkamiguru>To give some more context, I have guix running with qemu and am tryiing to passthrough the host filesystem using the -virtfs flag. When I run the standard mount command, it mounts the 9p filesystem correctly, but once I converted the mount command to a (file-system ...) block I can't seem to get it working. Here is a copy of the file-system block I
<superkamiguru>If I try and use the mount_tag as the device identifier, then system reconfiguration fails since the device isn't found. If I try to use another device that exists like /dev/null, then I get the 9p driver error that /dev/null isn't the correct channel (looking for mount_tag). From what I can tell the process is blocked because I need to pass
<superkamiguru>through the standard mount_tag as the device, but the device field wont let me.
<superkamiguru>Totally found the answer to my question. Looks like you can use 'file-system->mount-tag source' to specify mount tags