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: Mon, 28 Jun 2021 13:18:45 +0200 Message-ID: <2921d3d8-2d87-09e2-da01-e8c572054f4a@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7024841950957305098==" List-Id: --===============7024841950957305098== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Micahael, On 26/06/2021 14:27, Michael Tremer wrote: > No worries :) >=20 >> On 26 Jun 2021, at 13:26, Adolf Belka wrote: >> >> >> >> On 26/06/2021 14:22, Michael Tremer wrote: >>> Hey, >>> Did we intentionally drop the list from this conversation? >> >> Whoops sorry. No intention to drop the list, my fault. Fixed with this rep= ly. >> Adolf. >> >>>> 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 c= an finalise it for its release. >>>>>>> >>>>>>> There are loads of changes in it that may require a little bit of ext= ra testing. Especially the large amount of changes to the CGI files requires = some extra love, so I hope that everyone of you can find a couple of minutes = and 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= blog as usual. >>>>>>> >>>>>>> The next update will be put together by Arne who is now fully in char= ge of the next branch. It will come with the new kernel and to not make commu= nication too difficult, he will just take charge and put the whole thing toge= ther. >>>>>>> >>>>>>> We probably won=E2=80=99t have too much space because the kernel is g= oing to be quite large. However, there will be a new toolchain and loads of o= ther things coming with it, so if you have any patches towards that, please c= oordinate on the list and submit. >>>>>>> >>>>>>> Of course I would like to know what everyone has in the pipeline so t= hat we can schedule it accordingly. >>>>>> >>>>>> I am mostly just working on updates of packages that I discover are no= t 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 = python2 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 ot= her things. It would be great if we could get rid of Python 2 as soon as poss= ible. 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 go= ing to install it from the iso created in the build and then install the exp = kernel. However the git build from master now creates Core Update 158 and Arn= e's exp kernel readme says you have to do the install on top of Core Update 1= 57. >>> Yes, it breaks the IPsec page, but it should be fine for a development sy= stem. >>>> I have just, while writing this email, figured out how to get a git bran= ch in my local repository from core update 157. So will shortly re-do the bui= ld without crda and then install the iso into a vm in my testbed system and t= hen 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 rema= ining python2 modules to be removed within a day or so. The above worked. Yah. So the build to remove crda and all the rest of the py= thon2 modules is currently running. Hopefully patches being provided later today or tomorrow. Regards, Adolf. >>>> If the above doesn't work then I will be coming back for help. >>> Cool :) That sounds very good to me. >>> -Michael >>>> >>>> Regards, >>>> Adolf. >>>> >>>>>> https://patchwork.ipfire.org/patch/4376/ was submitted about 4 weeks a= go to fix bug #12441 but has not yet been committed. Not critical but would l= ike to know when it will move forward. >>>>> Arne is going to merge the next update together and I do not want to ge= t involved so that I do not cause any extra chaos. >>>>> -Michael >>>>>> >>>>>> Regards, >>>>>> >>>>>> Adolf >>>>>> >>>>>>> Best, >>>>>>> -Michael >=20 --===============7024841950957305098==--