From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark H Weaver <mhw@netris.org>
Subject: Re: python-3.3.5 test failures on i686 in core-updates
Date: Wed, 17 Sep 2014 07:27:21 -0400
Message-ID: <87ha06sd0m.fsf@yeeloong.lan>
References: <87k353tq8b.fsf@yeeloong.lan> <87fvfrtepv.fsf@yeeloong.lan>
	<8761gmblrj.fsf@gnu.org> <20140917110220.GB8046@debian.surfnet.iacbox>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33854)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mhw@netris.org>) id 1XUDQF-0003Se-3I
	for guix-devel@gnu.org; Wed, 17 Sep 2014 07:29:25 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mhw@netris.org>) id 1XUDQ8-0008E1-Qp
	for guix-devel@gnu.org; Wed, 17 Sep 2014 07:29:19 -0400
In-Reply-To: <20140917110220.GB8046@debian.surfnet.iacbox> (Andreas Enge's
	message of "Wed, 17 Sep 2014 13:02:20 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=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: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org

Andreas Enge <andreas@enge.fr> writes:

> On Wed, Sep 17, 2014 at 12:10:24PM +0200, Ludovic Court=C3=A8s wrote:
>> So now we have two option:
>>   1. Patch GCC 4.8.3 in core-updates, and rebuild the whole thing.
>>   2. Switch to GCC 4.9 as the default.
>> Option #1 is the safest, I think.
>
> As we need to rebuild everything anyway, how about trying out option 2?

We'd need to fix the GCC 4.9 build on mips64el first.

> In any case, before doing that, we should merge core-updates back to acti=
vate
> the security fix for glibc.

Given how broken things currently are on i686 in core-updates (broken
setresuid/setresgid in glibc =3D> python-3 test failures =3D> hundreds of
dependency failures of other important packages including emacs), I
don't see this as a good option for i686 users.

At minimum, we'd need to disable python-3 tests for i686, but even so, I
wonder what else will be broken due to the faulty setresuid/setresgid in
glibc.

      Mark