From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Release! Date: Thu, 30 Nov 2017 11:40:16 +0100 Message-ID: <878teo59tb.fsf@gnu.org> References: <877f16z9eo.fsf@gnu.org> <87infv54m3.fsf@gnu.org> <87efqgnn7x.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36340) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eKMGX-000411-PP for guix-devel@gnu.org; Thu, 30 Nov 2017 05:40:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eKMGT-0008T0-Dl for guix-devel@gnu.org; Thu, 30 Nov 2017 05:40:25 -0500 Received: from hera.aquilenet.fr ([2a0c:e300::1]:57645) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eKMGT-0008R9-04 for guix-devel@gnu.org; Thu, 30 Nov 2017 05:40:21 -0500 In-Reply-To: <87efqgnn7x.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 06 Oct 2017 20:30:10 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: guix-devel Hello! Time flies, but I think we=E2=80=99re about ready for the release. I=E2=80= =99d like to aim for next Tuesday (Dec. 5th) and fix small hickups and annoyances by then, particularly regarding GuixSD installation. Ricardo Wurmus skribis: >>> Here are some important items I can think of: > [=E2=80=A6] >>> =E2=80=A2 Guile 2.2 compiler terrible issue: >>> . There=E2=80=99s more going on on the Guile side, but for now the recent spl= it 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 =E2=80=98guix system init=E2=80=99 et al,= when compiling modules. I think a912c723f76d9762072ce27204a9227a64bcb625 removes most of these. >>> =E2=80=A2 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=E2=80=99ll have to work >>> on that incrementally. > > I guess we=E2=80=99ll be using berlin.guixsd.org instead of bayfront, no? Yes. Questions: 1. Do we pre-register berlin=E2=80=99s key on GuixSD? 2. Do we add berlin.guixsd.org to the list of substitute servers on GuixSD? On Guix? The drawback is that =E2=80=98guix=E2=80=99 sometim= es talks to both servers when retrieve substitute lists, which can be slightly slower/annoying, but otherwise I think it=E2=80=99s a win. Thoughts? The main GuixSD annoying messages that I think we should address by Tuesday are: 1. =E2=80=9CError in finalization thread: Bad file descriptor=E2=80=9D co= ming from the Shepherd; 2. =E2=80=9Cudevd[304]: RUN{builtin}: 'uaccess' unknown /gnu/store/q7c8ya= yywf76ai3sgvz16pmbz07gj4bp-udev-rules/lib/udev/rules.d/73-seat-late.rules:1= 5=E2=80=9D Both are harmless but they may give users a false sense that something=E2= =80=99s broken. Ludo=E2=80=99.