<foobarry>output path `/gnu/store/9s87z7j59w6cchy1xdmwcfy30812apan-edirect.tar.gz' should have sha256 hash `1cr3gzcs3flmgnnbj5iz93vh9w0fca1ilzi2q82cl63ln3mwvpz0', instead has `15zsprak5yh8c1yrz4r1knmb5s8qcmdid4xdhkh3lqcv64l60hli'
<rekado>re versions: I've been packaging the majority of the bioinfo stuff in the past, but for the past two months I've been excessively busy doing unrelated work. Since bioinfo tools are not that popular among Guix contributors they don't get updated as often as other packages.
<mark_weaver>civodul: bah, hydra's method of scheduling between jobsets is terrible. gnome-updates has 50 scheduling shares, and master has 100, but queue-runner just allocated *every* slot to gnome-updates
<mark_weaver>I have no idea how to prioritize master except to temporarily cancel all of the gnome-updates jobs :-(
<mark_weaver>after the important things are built on master, I'll restart the gnome-updates jobs
<civodul>mark_weaver: ISTR that individual jobs have a priority too, no?
<mark_weaver>civodul: yes, and I've gotten in the habit of setting those manually to direct hydra
<mark_weaver>civodul: but hydra only uses priorities to prioritize within a single jobset
<mark_weaver>it has some different mechanism to schedule between jobsets, and I guess that's what the jobset's "scheduling shares" is about, except that it doesn't seem to work properly.
<mark_weaver>very often I've seen queue-runner allocate all slots to a single jobset, even when multiple jobsets have pending jobs
<civodul>bah, i admit i never groked this "scheduling shares" thing
<mark_weaver>civodul: well, I'm just venting, no need to waste your time on this.
<jlicht>is someone currently using artanis 0.1.2 on guix? I'm having some weird issues, where the artanis store entry yet again has a gnu/store/asdfasdfasdf-artanis-0.1.2 dir, where the actual modules and binaries are located
<mark_weaver>civodul: I looked briefly at the queue-runner code, and might attempt to hack it a bit, although my perl-foo is rather weak these days :)
<adfeno>Welcome frafra. I'm not a Guix user, but I plan to be. :D
<frafra>adfeno, thank you too :) I waited many months before try to install guix sd
<adfeno>Besides, I sometimes help people with their questions, as long as I can find the needed information.
<frafra>I have a simple one: is it possible to change cflags?
<jmd>Am I correct in thinking that the messages from the substituter go to current-build-output-port ?
<mark_weaver>frafra: if you run guix directly from a git checkout (as most of us developers do, and I highly recommend), then you can run out of your own private git branch, with arbitrary modifications to guix, while easily integrating our upstream work into your branch
<mark_weaver>frafra: in that case, you can easily make global changes like that, but of course if you do that you'll have to build everything from source code yourself.
<mark_weaver>frafra: but we don't provide any easy way to set global compile-time preferences like that, analogous to gentoo USE flags
<suitsmeveryfine>mark_weaver: when I try to apply chown I get "Filesystem only readable"
<frafra>(I was asking because the hello packages looks different on my box)
<mark_weaver>suitsmeveryfine: on GuixSD we use some bind mount magic to make /gnu/store mounted read-only, to prevent people from accidentally editing things in there, which would lead to badness
<mark_weaver>suitsmeveryfine: did you edit something somewhere to set umask to 0?
<suitsmeveryfine>mark_weaver: the only thing I can think of is my my encrypted /home in the OS definition.
<ajgrf>mark_weaver: suitsmeveryfine: a similar thing happened to me last week, although i can't remember which package it was. i never did anything to fix it, just waited and tried the reconfigure again later with a new "guix-latest"
<mark_weaver>suitsmeveryfine: can you do "ls -l /gnu/store | grep rwx" to find out how many directories in there are writable?
<frafra>no code for module (gnu packages alsa-lib)
<frafra>I suppose I'm not specifying dependencies correctly
<ajgrf>suitsmeveryfine: unfortunately i've also garbage collected my system since then, so `ls -l /gnu/store | grep rwx` doesn't return anything noteworthy. just some packages which happen to include rwx in their hash
<mark_weaver>frafra: the alsa-lib package is in gnu/packages/linux.scm, a.k.a. (gnu packages linux)
<mark_weaver>frafra: you can find where a package is using "guix package -s"
<mark_weaver>in general, module (a b c) is found in a/b/c.scm within some directory in the load path
<mark_weaver>remember, with guix, if you already have a system installed that works, you can be reasonably certain that if you install a new system that's broken, you can still boot into an older version of the system
<alezost>there is "console-keymap-service" that can be specified in a system config, and as you pointed it is intended only for console (the same as "loadkeys ..." will do). X server can be started in various ways, I think it's up to a user to change a layout there
<Luoar>thanks for the answers and fir reminding me of setxkbmap :-)