From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: core-updates: Python build failures Date: Sat, 11 Mar 2017 19:05:09 -0500 Message-ID: <20170312000509.GA28022@jasmine> 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> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38635) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cmr0f-0007vf-6k for guix-devel@gnu.org; Sat, 11 Mar 2017 19:05:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cmr0c-00046z-3X for guix-devel@gnu.org; Sat, 11 Mar 2017 19:05:17 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:42845) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cmr0b-00046h-Re for guix-devel@gnu.org; Sat, 11 Mar 2017 19:05:14 -0500 Content-Disposition: inline In-Reply-To: <87innfk2yf.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> 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: Marius Bakke Cc: guix-devel@gnu.org --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAljEkLEACgkQJkb6MLrK fwjkgBAAkNVXmB8MH/UNMFkfWNVhe1TkLExHkoedWnYewrCL0GnLSMHulADYZyPX 75rPnjT5IdZnwTNZwVjUAaehZ0ep8ViTA1inFOEYiumFIBk0KWYrdFi9l2zBCja2 y0oqwvZZKxbKLDgcOJ9aJ9ckPIVPhtFe99RxPt/bgCpi48Cpf0I8bb4gi0+3rH/K D6PkozDxvjFeSzggpJtN+uqp1X31eLYT80lTW6vDDGZsKjjrxbJBqx5uIhL0hU6e lWKr8J34Qex2Z99pMN1jLs9GFWWQcYXnXgh0gCHCZcFaPUwjkUq4bGP1miBNQrho QcIvY7D1WvzZlp6D3TMoZ4IGsNbuVsGxkOjlQ98d/tc25txlc7Ri6lmM5Y8+yU/+ pnHF8cYdtOK+XQ6bFt2ZSnEhUUT+JGkewgltLCFNmwARp23z3gRs/tJvz6ubboEJ 9k6mbtmU3417sIXIe14jMaXuU4b5pfcEGqcILVgypLTocKuTQPzbapcdrEjMJy8c FFXMBYtc02eK+1CF3YeTh0dMcAD3SLK8mLg9Jsdlb2ErGg4gg3fX+7UxatezEuv5 sI4ZkH076LkuqseyhMfYA6HUSszganYON66YqQpXkvhYrcotHa71n9OCChubbJCi vsDFq9W1wmBoSq9xxr3poSxYBf92EYQr5fpCUmiKxmfj/gL2FC4= =Ejzh -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO--