<vagrantcish>axd-v: all i've got is (service libvirt-service-type (libvirt-configuration (unix-sock-group "libvirt"))) and adding the user to the libvirt group
<axd-v>vagrantcish: interesting. Someone earlier today was telling me about some bug and that they needed to have their user as part of the wheel group. I took it to mean that wheel is the only important group and replaced my unix-sock-group with "wheel" and this is the config that isn't working. I'll try adding the user to libvirt and then running the normal config like yours.
<vagrantc>ACTION wonders why /var/run vs. /run ...
<pkill9>out of interest, can you make a package without any source?
<pkill9>it does't let you omit the source field, or set it to #f, or set the origin to #f, I'm curious to know if it's possible
<pkill9>oh scratch that, a lot of packages do have source set to #f
<vagrantc>i'm curious about submitting an update for a new version of a package ... being new to guix and all that, not sure what the norms are with new upstream versions ... wouldn't make any other packaging changes.
<vagrantc>specifically, i'd like to see u-boot version 2018.05 (currently at 2018.01, and missed 2018.03 entirely)
<lfam>vagrantc: In general, we like to follow upstream's recommendations. So, if we have the humanpower to do normal Guix packaging QA processes, and the update does not cause too many depending packages to be rebuilt, we do the update.
<lfam>So, if 2018.05 is the newest release (or at least newer than what we have), and it works for you, we should update it.
<vagrantc>lfam: e.g. feel free to submit version updates after some testing?
<lfam>" and the update does not cause too many depending packages to be rebuilt": This can be checked with `guix refresh --list-dependent foo`. We aim to cause <300 rebuilds for package updates on the master branch
<vagrantc>ACTION will build test u-boot-* and test a couple boards
<lfam>Reading the source of (gnu packages bootloaders), I see that the u-boot package isn't public. But you can still list its dependents like this: `guix refresh --list-dependent --expression='(@@ (gnu packages bootloaders) u-boot)'`
<thomassgn>anyone know how I could figure out if program X is part of my system? I would like to know if the xdg-user-dirs is installed and used by my system, but I can't see it in my path or anything...
<thomassgn>I see it's not even in my store, so it's not on my system.