<ng0>I talked with someone at the hackerspace I go to.. it's unfortunate that they decided to not publish their sources yet (moving around code) because I think it's a nice project and they need people to work on the code.. though they should tranlate their website :)
<ng0>if someone knows how to read german: http://www.happyhydro.org/ otherwise I think you can contact them directly via email. site is a bit broken too and lacks the presentations and talks they gave etc
<rekado>civodul: it seems that we still have a lot of jobs in core-updates that should be restarted but haven’t. Many of them are marked as failed due to the tcsh failure, which has already been fixed.
<efraim>gtk+ hash mismatch: I sent an email to Sou about it
<efraim>looks like it got updated and pushed directly to core-updates, so I don't think it was built by hydra previously
<thomasd>yes, I was thinking about similar use cases (apart from simple convenience of being able to install and manage software at will). also writing custom Guix packages for our own codes can really help to clearly establish dependencies and code versions used in processing chains etc.
<thomasd>thanks for the articles. I'll think about how to present the case in order to convince our sysadmin :)
<thomasd>I'll keep you updated if I have useful feedback or would need some help
<Digit>many eyes make all bugs shallow. if only a corporation can see the code, and those who've seen the leaked code but cannot reveal they have openly, code whose notion of protection is merely obscurity... then i think that's a more vulnerable position. to those only accustomed to "security through obscurity", code anyone can see may at first seem daunting, but in time, you'll see it evolves more strongly, that anyone can find the bugs
<citronputride>Digit, i didn't search for a list of virus on linux. But your previous answer helped (is it english?) me
<Digit>my french is terrible, so i have no idea if this online translation is accurate: il y a plus de découragement pour mettre intentionnellement des trous de sécurité dans le logiciel libre. il n'y a plus d'incitation à faire des trous de sécurité dans le logiciel propriétaire, pour le profit et le pouvoir-sur.
<reepca>where in the git repository can I find the file desktop.scm that would be located at /etc/configuration/desktop.scm if I were using an installation image? I searched for it but could only find one at gnu/services/desktop.scm
<ZombieChicken>lfam: guix may not depend on it, but some build processes seem to
<ng0>ZombieChicken: Gentoo openrc based or systemd variant? for the overlay, the openrc service is sh***. if you can fix it, be welcome and send a patch my way. also, not everyone on irc is a 'his' :), so 'they' works better
<lfam>ZombieChicken: I just built our gawk package successfully for x86_64 from the current HEAD of our master branch (bfb48f4f335). So you should be able to build it for that architecture from that commit, too.
<ZombieChicken>as it in doesn't actually do what it is supposed quite frequently
<lfam>And the gawk package does not include util-linux / more in its package definition
<ZombieChicken>lfam: Well, I'm currently removing guix to merge it from the ebuild