<efraim>So aarch has freedreno and no Intel, Intel platforms the opposite
<efraim>I'll check what people have and prepare a patch today
<ryanwatk`>Hi guys, I would really like to define an 'emacs server' service for a guixsd machine of mine, I presume it is doable somehow in the OS definition, does anybody have any idea how it would look? Should I look to the shepherd manual?
<ryanwatk`>Likewise, I figured some screen sort of daemon service would also be nice. My home environment involves many systems so I wanted to offload a lot of system resources to the non embedded devices :D
<rekado>efraim: is there a way to build the mesa drivers in a separate package?
<efraim>rekado: possibly, but I think (match (%current-system) ... is the best option, this way everyone gets the drivers that they can actually use and its all in one package
<efraim>currently we already drop the i915 dri-driver for non-intel systems, this just extends it for all the architectures and for the gallium-drivers too
<thomasd>about the update mechanism, an option to update to a version for which substitutes are available, would be nice (at least some point, maybe we'd need more build infrastructure to make that work well?)
<thomasd>this is probably obvious, but I haven't read the remark anywhere else, so thought I'd mention it anyway :)
<thomasd>I wonder how others deal with substitutes and updates? I look which commits have been evaluated on hydra.gnu.org, checkout one of those in git, and upgrade from that.
<rekado>I just don’t know what rule executes a piece of code.
<rekado>it’s an R snippet that’s run at build time; if I remove handling of timestamps there I might actually break runtime code, so I’m trying to find a way to just reset the mtime of generated files right before the code is run.
<rekado>it’s an unfortunate downside to code reuse.
<lfam>Well... doing. Hopefully the HTTP request goes through
<rekado>bavier`: I can’t reproduce the logo truncation error in icecat :(
<thomassgn>my laptop keeps crashing during some of the heavier builds due to overheating. I've added max-jobs=1 and cores=2. The laptop is an hp elitebook i7 4G ram and I have been running both nixos and gentoo (everything compiled) fine earlier. I find MCE messages in my logfiles, but can't make much out of them. Any tips for checking build daemons current settings or getting more info from MCE/Kernel?
<civodul>thomassgn: i have the same laptop running GuixSD but i haven't seen this
<thomassgn>lfam: haha, nice. I think it's overheating, but I haven't been able to pinpoint much, I don't even know what happens at boot in my logs so the messages from MCE may be unrelated. But I just started the MCE daemon manually (didn't look like it was running from 'sudo herd status'). Am retrying to build system; as there now is a new mcelog file in /var/log/ ....
<buenouanq>man, just as I mentioned the EOMA68, it gets pushed back a couple months (;-___-)
<buenouanq>efraim: I've yet to successfully get ibus working on GuixSD at all...
<buenouanq>So, I have a postgres service running, but this obviously didn't install all the tools (things every tutorial mentions) I need to access it from whatever user. In addition to the service, am I supposed to install the postgres package under said user?