Marius Bakke <mba...@fastmail.com> skribis: > Leo Famulari <l...@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: >>> >>> https://hg.python.org/cpython/rev/337461574c90 >>> >>> 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’s what we build glibc against (via ‘--enable-kernel’). (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’ll see how it goes: https://hydra.gnu.org/jobset/gnu/core-updates#tabs-evaluations Ludo’.
