<leoprikler>so you could write (modify-services %desktop-services (delete gdm-service-type) (add slim-service-type [config]))
<atka>ok, trying it out, we'll see if I did it right.
<leoprikler>and under the hood that would be translated into (cons* (service slim-service-type [config]) (old-modify-services ...))
<atka>also when issuing guix reconfigure after a change to config.scm does it always take so long? I just did it a minute ago and now I only changed a line yet it is downloading a bunch of stuff again?
<leoprikler>another neat, albeit probably obscure feature would be (old-service-type => [new-service-type] new-service-config)
<jeko>is there a way to specify additionnal channels in a system definition ?
<jeko>like the one I have in .config/guix/channels.scm
<dragestil>since guix can be used for configuration management, does this mean people normally don't use ansible to configure guix machines?
<sneek>mothacehe, bricewge says: Would it be possible to have RSS feed from Curiass per build history? So that a person interested in, say the "hello" package, can follow updates and failing builds of that package.
<jeko>I am wondering if I can add a custom channel to a system definition ? to replace the need to edit ~/.config/guix/channels.scm
<ecraven>hm.. can I somehow get the guix builder to put the .git directory into the building directory? this tool uses git log to check for the current version. I have (method git-fetch) and (uri (git-reference ...) ...)
<efraim>you'll have to patch it. We delete the .git directory as part of git-fetch
<PurpleSym>rekado_: Yeah, good idea preparing for the upcoming v4.1.1. Pushed. I also saw two references to /bin/sh, but not sure yet how to test this from the R side (R_system_timeout and R_popen_timeout).
<rekado_>PurpleSym: hmm, re the missing issue: it’s not mumi’s problem. The mails haven’t been transferred from the debbugs server.
<mothacehe>I had to restart Cuirass this morning because of this error: "Git error while fetching inputs of 'version-1.3.0': "SSL error: syscall failure". It would be nice if Cuirass was robust to this kind of errors. I'll report it on bug-guix I guess.
<ecraven>how does guix system docker-image work? I'm trying 'guix system docker-image ./config.scm'
<ecraven>how is it started? does it need any parameters?
<roptat>the bootloader passes the arguments to the kernel, it lets it know about its location
<ecraven>I'm trying to understand how I would run the shepherd in a container, so without actually booting
<roptat>you could use "guix system docker-image" or "guix system container", that would be simpler I think
<ecraven>so guixsd just starts '/gnu/store/655wq4zm0j9fh05xzzr1hc6a2z5y8dra-shepherd-0.8.1/bin/shepherd'?
<ecraven>that doesn't produce an lxc image that I can run
<ecraven>also, guix system docker-image doesn't actually work here, it fails while running inside the VM for building
<roptat>not exactly, in my case, it uses an initrd that contains the shepherd and stuff, and runs the boot script from it (/gnu/store/3ssf75i8dz1zqzyszlkckwcairdy55cy-system/boot, but the location changes at every update)
<ecraven>hm.. so in the end, it might be rather hard to actually boot without a full boot?
<ecraven>I'll try to get a docker image built, and see what that does
<roptat>I managed to run a guix system from a chroot once...
<roptat>but the shepherd was not working, I had to run my daemons by hand
<ecraven>why does guix system docker-image start a VM? shouldn't it just start adding layers?
<ecraven>how does guix deal with loading .so files dynamically? how does a program find them?
<ecraven>if shepherd says "failed to start service", where can I see *why* it failed?
<Gooberpatrol66>are you supposed to use berlin.guix.gnu.org and ci.guix.info as substitute servers?
<Gooberpatrol66>the keys are in the directory with ci.guix.gnu.org and bordeaux.guix.gnu.org but they aren't enabled by default
<cybersyn>hiya guix, i just want to report that while my first install of guix was a bit confusing last November (having first tried the TUI installer then, but having to resort to manual config), I just did a clean install on the same machine (2010 iMac) with the TUI interface and it installed without a problem or a gnuissance, and that feels like a real massive leap for the system.
<civodul>ecraven: .so are searched for in the "normal" way: $LD_LIBRARY_PATH first (if defined), then DT_RUNPATH for ELF files
<civodul>jorge[m]123: pero no veo ningún error aquí
<roptat>Gooberpatrol66, you installed guix on a foreign distro with the script? It should have asked whether you want to use substitute servers or not. If you said yes, it should have authorized the keys, otherwise try "guix archive --authorize < /path/to/the/key.pub"