<darkpsi>hey having some trouble getting xmonad to work the slim does not seem to know how to handle xmonad has any one got xmonad working?
<atw>darkpsi: what's the issue, from the perspective of slim?
<darkpsi>well not sure how familur you are with xmonad but xmonad compiles a binary to then execute as the wm (like a few other wm) when i select xmonad on the slim it fails to execute a wm and does not use the binary or xmonad.hs file in my ~/.xmonad directory
<darkpsi>can not find too much infomation on configuring xmonad on guix
<buenouanq>the manual configuration info for the certbot service is not inline with the service itself
<buenouanq>has erroneous fields like `name' which seems to have been changed instead to `certificates'
<vagrantcish>so, i installed libvirt, added a service for it, and it started running. had some issues connecting to it with virt-manager that seemed to be polkit related. but after a reboot, libvirtd gets disabled, respawning too fast...
<vagrantcish>i'm not sure where to look for information about why it's restarting ... /var/log/messages is pretty minimalistic
<sneek>catonano, ArneBab says: autotools is pretty nice, but it is hard to find clear documentation because lots of half-truths are floating around the net and it misses clear guides "how to do X nicely with autotools".
<vagrantcish>both libvirtd is running, and my user in the libvirt group can access it
<zero21>did i understood right that: to create a new package that isnt in guix repository and definiton of that package was made with use of guix import command, i will have to do "git clone https://git.savannah.gnu.org/git/guix.git" to get pre-inst-env script without which it is not possible to make packages. Or i am mistaken?
<zybell>it is not possible to make packages *the way you have chosen* without pre-inst-env
<snape>buenouanq: yw! Basically, certbot has many ways to renew the certificates. The one we chose is to place authentication files in Nginx's webroot. We chose it for its simplicity. It's not ideal, but it works for now.
<snape>It's not ideal because it requires a web server to be running.
<snape>vagrantcish: yes, it's the intended use. It will fail, but later.
<rekado>vagrantcish: I’d use GUIX_PACKAGE_PATH instead.
<vagrantcish>oh, yes, that's much nicer. not having to rebuild guix every time you tweak a package...
<ngz>Hello. I'm trying to package some software that requires PyQt. I added it to the dependencies and build is ok. However, when trying to run the software I get the error "pkg_resources.DistributionNotFound: The 'PyQt5<5.10,>=5.9' distribution was not found".
<ngz>I guess I have to somehow point to the appropriate location for PyQt at run time, too.
<vagrantcish>i should probably actually read some guile intros or something at this point
<taylan>is there something like 'guix pull' for the system-installed guix? the closest thing I can think of is running 'guix pull' and 'guix system reconfigure /etc/config.scm' as root, which will make the system-installed guix almost up-to-date but not entirely :)
<taylan>buenouanq: my understanding is that this will install the version of guix that's currently declared latest in the package DB, which can't be the latest commit because of the chicken-and-egg problem. (in theory it could be the fore-last commit, but that would mean you need to update the guix recipe with every single commit to reference the previous commit, which obviously isn't done.)