From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Core Update 158 and beyond Date: Sat, 26 Jun 2021 14:26:56 +0200 Message-ID: <381ca4b9-ba20-ce9c-1192-88b88b962c9a@ipfire.org> In-Reply-To: <28E9F021-D5D0-4F1E-BC69-53F8043E4E24@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1745948159062955957==" List-Id: --===============1745948159062955957== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 26/06/2021 14:22, Michael Tremer wrote: > Hey, >=20 > Did we intentionally drop the list from this conversation? Whoops sorry. No intention to drop the list, my fault. Fixed with this reply. Adolf. >=20 >> On 26 Jun 2021, at 13:20, Adolf Belka wrote: >> >> Hi Michael, >> >> On 26/06/2021 13:41, Michael Tremer wrote: >>> Hello, >>>> On 24 Jun 2021, at 17:17, Adolf Belka wrote: >>>> >>>> Hi Michael, >>>> >>>> On 22/06/2021 14:17, Michael Tremer wrote: >>>>> Hello everyone, >>>>> >>>>> Yesterday, I merged the upcoming Core Update into master so that we can= finalise it for its release. >>>>> >>>>> There are loads of changes in it that may require a little bit of extra= testing. Especially the large amount of changes to the CGI files requires so= me extra love, so I hope that everyone of you can find a couple of minutes an= d click as many buttons as possible and see whether things are working fine. = If not, please report here. >>>>> >>>>> I will work on a change log as soon as possible and publish it on the b= log as usual. >>>>> >>>>> The next update will be put together by Arne who is now fully in charge= of the next branch. It will come with the new kernel and to not make communi= cation too difficult, he will just take charge and put the whole thing togeth= er. >>>>> >>>>> We probably won=E2=80=99t have too much space because the kernel is goi= ng to be quite large. However, there will be a new toolchain and loads of oth= er things coming with it, so if you have any patches towards that, please coo= rdinate on the list and submit. >>>>> >>>>> Of course I would like to know what everyone has in the pipeline so tha= t we can schedule it accordingly. >>>> >>>> I am mostly just working on updates of packages that I discover are not = up to date. Nothing really time critical although all good to get updated. >>>> >>>> gd (problems with pie charts - separate email sent on this topic) >>>> iperf3 >>>> libxcrypt >>>> sqlite >>>> Test-Tabs+Wrap >>>> nfs >>>> >>>> I am also shortly going to work on crda to enable removal of the last py= thon2 packages but that has to wait to be merged until a kernel at version 4.= 15 or later gets merged. So again not time critical. >>> I wanted to bring this up recently but got overwhelmed with loads of othe= r things. It would be great if we could get rid of Python 2 as soon as possib= le. What is the status on this? How can I help to make this happen? >> >> I started working on it yesterday, I ran a build without crda and was goin= g to install it from the iso created in the build and then install the exp ke= rnel. However the git build from master now creates Core Update 158 and Arne'= s exp kernel readme says you have to do the install on top of Core Update 157. >=20 > Yes, it breaks the IPsec page, but it should be fine for a development syst= em. >=20 >> I have just, while writing this email, figured out how to get a git branch= in my local repository from core update 157. So will shortly re-do the build= without crda and then install the iso into a vm in my testbed system and the= n install the exp kernel and see if it works with the country code. >> >> If the above works then I should be able to provide a patch for the remain= ing python2 modules to be removed within a day or so. >> If the above doesn't work then I will be coming back for help. >=20 > Cool :) That sounds very good to me. >=20 > -Michael >=20 >> >> Regards, >> Adolf. >> >>>> https://patchwork.ipfire.org/patch/4376/ was submitted about 4 weeks ago= to fix bug #12441 but has not yet been committed. Not critical but would lik= e to know when it will move forward. >>> Arne is going to merge the next update together and I do not want to get = involved so that I do not cause any extra chaos. >>> -Michael >>>> >>>> Regards, >>>> >>>> Adolf >>>> >>>>> Best, >>>>> -Michael >=20 --===============1745948159062955957==--