Hello! Time flies, but I think we’re about ready for the release. I’d like to aim for next Tuesday (Dec. 5th) and fix small hickups and annoyances by then, particularly regarding GuixSD installation.
Ricardo Wurmus <rek...@elephly.net> skribis: >>> Here are some important items I can think of: > […] >>> • Guile 2.2 compiler terrible issue: >>> <https://lists.gnu.org/archive/html/guile-devel/2017-05/msg00033.html>. There’s more going on on the Guile side, but for now the recent split of the big package files has helped reduce peak memory consumption noticeably. > One annoyance is that after compiling one file it prints this message: > > Some deprecated features have been used. Set the environment > variable GUILE_WARN_DEPRECATED to "detailed" and rerun the > program to get more information. Set it to "no" to suppress > this message. This was also showing up a lot in ‘guix system init’ et al, when compiling modules. I think a912c723f76d9762072ce27204a9227a64bcb625 removes most of these. >>> • Prepare to migrate to the new build farm: the hardware of >>> bayfront.guixsd.org has been fixed (it was unreliable until we >>> changed its CPUs), so now we need to fix a couple of issues in >>> Cuirass and generally improve it so we can, via its HTTP interface, >>> add new jobsets and so on. Of course we’ll have to work >>> on that incrementally. > > I guess we’ll be using berlin.guixsd.org instead of bayfront, no? Yes. Questions: 1. Do we pre-register berlin’s key on GuixSD? 2. Do we add berlin.guixsd.org to the list of substitute servers on GuixSD? On Guix? The drawback is that ‘guix’ sometimes talks to both servers when retrieve substitute lists, which can be slightly slower/annoying, but otherwise I think it’s a win. Thoughts? The main GuixSD annoying messages that I think we should address by Tuesday are: 1. “Error in finalization thread: Bad file descriptor” coming from the Shepherd; 2. “udevd[304]: RUN{builtin}: 'uaccess' unknown /gnu/store/q7c8yayywf76ai3sgvz16pmbz07gj4bp-udev-rules/lib/udev/rules.d/73-seat-late.rules:15” Both are harmless but they may give users a false sense that something’s broken. Ludo’.
