From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: 0.6 is around the corner! Date: Tue, 01 Apr 2014 21:25:18 +0200 Message-ID: <87fvlwn97l.fsf@gnu.org> References: <877g7futo0.fsf@gnu.org> <87y4zokho0.fsf@yeeloong.lan> 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]:51500) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WV4Je-0000sF-FE for guix-devel@gnu.org; Tue, 01 Apr 2014 15:27:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WV4JG-0000L7-Dx for guix-devel@gnu.org; Tue, 01 Apr 2014 15:25:46 -0400 Received: from hera.aquilenet.fr ([2a01:474::1]:55460) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WV4JG-0000KH-57 for guix-devel@gnu.org; Tue, 01 Apr 2014 15:25:22 -0400 In-Reply-To: <87y4zokho0.fsf@yeeloong.lan> (Mark H. Weaver's message of "Tue, 01 Apr 2014 14:50:55 -0400") 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Mark H Weaver Cc: guix-devel@gnu.org Mark H Weaver skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > >> 0.6 is getting ready! The remaining items are Mark=E2=80=99s new union.= scm, and >> Nikita=E2=80=99s signed-substitutes support. >>=20=20=20 >> I think we can expect to have them in shape within a few days, hopefully. >> So it=E2=80=99s definitely time to report any issues you may have. > > I've run into a build issue with recent master on x86_64 and Loongson 3A > (both hosted on Debian wheezy). Python 3 fails in the tests with > "OSError: out of pty devices" Any idea what this test is doing? (Maybe Cyril knows?) > and then the guix-daemon sometimes gets stuck in a sleeping state and > hangs indefinitely. How does that happen? Could you get a backtrace next time it shows up, and ideally a way to reproduce? > My Loongson 2F system, based on 1eefbb2693f0f29f8f095af9f067240b85e735aa > with some cherry-picks and local patches, did not run into this problem. > My guess is that a commit since 1eefbb2 broke things. One candidate is 9a9a3ad (=E2=80=9CEnable tests in Python 3.=E2=80=9D). > Beyond that, here are some things that I'd ideally like to get into 0.6: > > * New union.scm. Definitely. The last draft you posted looked OK to me; I can write test sometime before or after you push it. > * Fix more packages to install man pages in share/man: expect, lua, zip, > pth, bazaar, ocaml, indent, netpbm. OK, but that shouldn=E2=80=99t be blocking. > * Look into security updates for mutt, file, and libssh: > file: https://github.com/file/file/commit/c0c0032b9e9eb57b91fefef905a3b= 018bab492d9 > mutt: Debian Security Advisory DSA-2874-1 > libssh: Debian Security Advisory DSA-2879-1 Yes, makes sense. Thanks for keeping track of that! Ludo=E2=80=99.