From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Core Update 158 and beyond Date: Sat, 26 Jun 2021 13:27:11 +0100 Message-ID: In-Reply-To: <381ca4b9-ba20-ce9c-1192-88b88b962c9a@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8589724901096497098==" List-Id: --===============8589724901096497098== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable No worries :) > On 26 Jun 2021, at 13:26, Adolf Belka wrote: >=20 >=20 >=20 > On 26/06/2021 14:22, Michael Tremer wrote: >> Hey, >> Did we intentionally drop the list from this conversation? >=20 > Whoops sorry. No intention to drop the list, my fault. Fixed with this repl= y. > Adolf. >=20 >>> On 26 Jun 2021, at 13:20, Adolf Belka wrote: >>>=20 >>> Hi Michael, >>>=20 >>> On 26/06/2021 13:41, Michael Tremer wrote: >>>> Hello, >>>>> On 24 Jun 2021, at 17:17, Adolf Belka wrote: >>>>>=20 >>>>> Hi Michael, >>>>>=20 >>>>> On 22/06/2021 14:17, Michael Tremer wrote: >>>>>> Hello everyone, >>>>>>=20 >>>>>> Yesterday, I merged the upcoming Core Update into master so that we ca= n finalise it for its release. >>>>>>=20 >>>>>> There are loads of changes in it that may require a little bit of extr= a testing. Especially the large amount of changes to the CGI files requires s= ome extra love, so I hope that everyone of you can find a couple of minutes a= nd click as many buttons as possible and see whether things are working fine.= If not, please report here. >>>>>>=20 >>>>>> I will work on a change log as soon as possible and publish it on the = blog as usual. >>>>>>=20 >>>>>> The next update will be put together by Arne who is now fully in charg= e of the next branch. It will come with the new kernel and to not make commun= ication too difficult, he will just take charge and put the whole thing toget= her. >>>>>>=20 >>>>>> We probably won=E2=80=99t have too much space because the kernel is go= ing to be quite large. However, there will be a new toolchain and loads of ot= her things coming with it, so if you have any patches towards that, please co= ordinate on the list and submit. >>>>>>=20 >>>>>> Of course I would like to know what everyone has in the pipeline so th= at we can schedule it accordingly. >>>>>=20 >>>>> 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. >>>>>=20 >>>>> gd (problems with pie charts - separate email sent on this topic) >>>>> iperf3 >>>>> libxcrypt >>>>> sqlite >>>>> Test-Tabs+Wrap >>>>> nfs >>>>>=20 >>>>> I am also shortly going to work on crda to enable removal of the last p= ython2 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 oth= er things. It would be great if we could get rid of Python 2 as soon as possi= ble. What is the status on this? How can I help to make this happen? >>>=20 >>> I started working on it yesterday, I ran a build without crda and was goi= ng to install it from the iso created in the build and then install the exp k= ernel. 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 15= 7. >> Yes, it breaks the IPsec page, but it should be fine for a development sys= tem. >>> I have just, while writing this email, figured out how to get a git branc= h in my local repository from core update 157. So will shortly re-do the buil= d without crda and then install the iso into a vm in my testbed system and th= en install the exp kernel and see if it works with the country code. >>>=20 >>> If the above works then I should be able to provide a patch for the remai= ning python2 modules to be removed within a day or so. >>> If the above doesn't work then I will be coming back for help. >> Cool :) That sounds very good to me. >> -Michael >>>=20 >>> Regards, >>> Adolf. >>>=20 >>>>> https://patchwork.ipfire.org/patch/4376/ was submitted about 4 weeks ag= o to fix bug #12441 but has not yet been committed. Not critical but would li= ke 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 >>>>>=20 >>>>> Regards, >>>>>=20 >>>>> Adolf >>>>>=20 >>>>>> Best, >>>>>> -Michael --===============8589724901096497098==--