From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: core-updates: Python build failures
Date: Mon, 13 Mar 2017 09:30:30 +0100
Message-ID: <87mvcpd1eh.fsf@gnu.org>
References: <87mvdpw3b3.fsf@gnu.org> <20170309223337.GA7931@jasmine>
	<87r324kdol.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
	<20170311172104.GA30965@jasmine>
	<87innfk2yf.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
	<20170312000509.GA28022@jasmine>
	<87efy2jso7.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
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]:48646)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1cnLNF-0007vh-1q
	for guix-devel@gnu.org; Mon, 13 Mar 2017 04:30:38 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1cnLNA-0008DJ-VW
	for guix-devel@gnu.org; Mon, 13 Mar 2017 04:30:36 -0400
In-Reply-To: <87efy2jso7.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
	(Marius Bakke's message of "Sun, 12 Mar 2017 18:44:56 +0100")
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" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org

Marius Bakke <mbakke@fastmail.com> skribis:

> Leo Famulari <leo@famulari.name> writes:
>
>> On Sat, Mar 11, 2017 at 08:50:32PM +0100, Marius Bakke wrote:
>>> I tried applying the upstream fix for 3.5:
>>>=20
>>> https://hg.python.org/cpython/rev/337461574c90
>>>=20
>>> However, the monster patch does not apply.
>>
>> [...]
>>
>>> Will try to dig out the other patches from 3.5 branch that this depends
>>> on tomorrow. I can't reproduce the getentropy() failure either,
>>> apparently it only occurs on kernels < 3.17.
>>
>> Maybe we should update Python 3.5 instead, so that the patch applies. Or
>> update the kernels on the build farm machines.

In general, our packages should work with kernels as old as 2.6.32,
since that=E2=80=99s what we build glibc against (via =E2=80=98--enable-ker=
nel=E2=80=99).
(We should probably bump to something a bit newer though.)

> Oh, I missed that 3.5.3 is out. After updating, the patch applied.
>
> I've pushed the Python update and the getentropy() fix as
> 343cee8af and e4d34cd0 respectively.

Awesome, thanks!

I started an evaluation of core-updates, we=E2=80=99ll see how it goes:

  https://hydra.gnu.org/jobset/gnu/core-updates#tabs-evaluations

Ludo=E2=80=99.