<sturm>I can run curl against the URL and get the publish default page back
<sturm>I've just tried setting up the publish server as a service with just "(service guix-publish-service-type)". Logs say that it's been disabled for respawning too fast, though no hint as to the error. I've tried removing and recreating the signing key.
<apteryx>I'm good too! I just finished installing myself at my new place. Thrilled to restart hacking on Guix!
***pksadiq_ is now known as pksadiq
<PlainDave>I've downloaded guixsd-usb-install-0.13.0.x86_64-linux.xz, but I don't know what to do with it. I've installed most of the Ubuntu flavors successfully. Do I change the file extension to .iso?
<rekado>so… I was told that we have yet another rack full of unused servers; a bit more recent hardware than the old Sun hardware of berlin.guixsd.org. As soon as IT wires up the rack switch I can get to install an extension to berlin.guixsd.org.
<rekado>Also: next week we’ll retire a couple of servers that will then go straight to berlin.guixsd.org.
<kmicu>brendyn: Do you keep your Emacs config in a version control system? Maybe you could rollback to previously working versions.
<brendyn>kmicu: I think it has been present for a long time. the bug does not occur all the time I'm not sure how to reliably reproduce it. I thought it maybe occured when i copied and unbalanced ( or " it doesnt break when i try to reproduce it
<ng0>I'll try it on the server once it is done with this pull.. first probably succesful pull in 12 months
<ng0>I think parts of the reason why compiling is taking so long are a) the little RAM and b) at some point people all over the world started using s.n0.is running searx instance like rabbits on a bad trip down to wonderland.
<ng0>keep the logs for a week and shred them afterwards, what could go wrong... watching the queries live I feel like Google. It's good that I don't pay anything for bandwidth
<civodul>so, anyone willing to try "guix pull --branch=wip-pull-reload"?
<civodul>it won't eat your computer, i promise! :-)
<ng0>give it probably 12 more hours and I can report :)
<bavier>vagrantc: but you could just run the build command as root also
<vagrantc>i like not having to gain root privledges unecessarily
<vagrantc>so i was liking, at least in theory, the build as user, install as root workflow
<vagrantc>though even the root's builds happen as other users, for the most part
<vagrantc>still, executing as little code as root as possible, generally a good principle
<bavier>vagrantc: right, you'd be communicating with the daemon, which is already running with root privileges, and the permissions are dropped as soon as possible for the actual builds
<vagrantc>so, following the desktop.scm shipped with the installer... i end up with gnome and xfce with slim as a display manager ... is this intentional as the recommended display manager for guixsd rather than gdm or lightdm or whatever?
<vagrantc>or is it more of a lowest common denominator?
<vagrantc>ACTION isn't choosy with display managers, as long as they work
<vagrantc>and i haven't had problems with slim, per se