<rgrau>oh... I got confused... thought the newly released one was 24.5
<rgrau>after installing 'guixOS' (or, what's the name of the distro?), I installed xorg-server, but when I try to run 'X'it fails to start (I guess it's because I haven't configured anything...) any pointers to what to do to configure X?
<rgrau>years ago there was a tool that generated Xorg.conf file (which I forgot it's name), but anyway, AFAIK nowadays xorg.conf file is obsolete, no?
<davexunit>rgrau: I don't start X manually, but use the slim-service in my OS config file
<rgrau>oks, I see there's a section in the manual for it... when I installed guix distro I did it with the exact minimal example file that came with it
<rgrau>I guess there's a way to update the file and say 'update to this state' ... (blind guessing)
<DusXMT>(But in the case of Virtualbox, I think it needs to be converted into VDMI, which is not hard to do, just google `convert raw image to vdmi' (or is the format called something else?), and add that as a second hard drive and boot from it)
<jmd>Do builds on hydra get triggered by commits or what?
*nebuli nods; should have a patch proposal today or tomorrow, making both options available makes for more complex input validation
<mark_weaver>civodul: I was confused about it as well. The "Invoking guix-daemon" node of the manual states that the defaults for --cores and --max-jobs are both 1. That may be true, but it will leave users scratching their heads, I think.
<mark_weaver>It would be helpful to have a way to actually enforce serial builds, one at a time.
<nebuli>making client not override daemon settings would be good, too, but i'll settle for not frying my laptop as a first step... default guix-daemon settings of unlimited jobs and cores lead to n^2 phenomen…
<taylanub>apparently nmap uses GPLv2 but its COPYING file has a header with some additional text: https://svn.nmap.org/nmap/COPYING how should I proceed? it talks about special exceptions to the GPL, which I thought were prohibited by the GPL, or is that just v3?