From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Core Update 157 Date: Mon, 17 May 2021 22:53:59 +0100 Message-ID: <04B10831-87CE-433C-BD5B-659EA2AF48B7@ipfire.org> In-Reply-To: <36ab2dee-02e8-6cad-ff97-b4f1a6e9ffd6@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5693551720041636016==" List-Id: --===============5693551720041636016== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 17 May 2021, at 22:52, Adolf Belka wrote: >=20 > Hi Michael, >=20 > I don't have anything new that I am working on that needs to go into 157. I= just keep finding things that can be updated and so I update them. I am quit= e happy for you to decide which Core Update they should go in. Cool. > In terms of python2 the big barrier to removing python2 at some point is cr= da. From my investigation it requires the python2 version of M2Crypto. The py= thon2 version of M2crypto requires the python2 versions of typing and setupto= ols. All the other python2 to python3 migrations seemed to go okay. I have seen your email. I just don=E2=80=99t manage to stay on top of my inbo= x at the moment. I will reply to that as soon as I can. -Michael > Regards, >=20 > Adolf. >=20 > On 17/05/2021 23:23, Michael Tremer wrote: >> Hello, >>=20 >> Because there are so many things going on at the same time, I would like t= o start a brief main thread about the upcoming Core Update(s). >>=20 >> The original plan was to have this closed a while ago because Core Update = 156 has already gone out. But then I decided to wait for a couple of smaller = things until we had a security vulnerability reported which I wanted to inves= tigate more (#12616 and #12619). It is not too bad, but I would like to ship = at least a fix that is good enough to mitigate it. We might need some more ti= me to figure out the details around the other half of the solution for this p= roblem. >>=20 >> Now this update has become *very* large. It is the largest update we have = ever had and that might break things. Therefore I do not want to merge anythi= ng more that has to go into the core system, but add-on packages are fine. >>=20 >> In fact, the build that I just pushed should be the final one, unless we f= ind any other problems. Does anyone have anything urgent and small left? Othe= rwise Core Update 158 will be open as soon as 157 has hit the master branch. >>=20 >> In order to coordinate that a little bit more and have a good and hopefull= y brief merge window, what should be in it? >>=20 >> * Fixes for #12616 >> * Can we finish the migration away from Python 2? >> * Drop the packages discussed at the last conference call (https://wiki.ip= fire.org/devel/telco/2021-05-03)? >> * VPNs for iOS (https://patchwork.ipfire.org/project/ipfire/list/?series= =3D1323)? >>=20 >> What else are you guys working on that is ready for prime-time? >>=20 >> -Michael --===============5693551720041636016==--