From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: The Upcoming Core Update(s) Date: Tue, 21 Nov 2023 20:39:00 +0000 Message-ID: <76bf3e38-f21e-4ff7-86a0-0801b0067bca@ipfire.org> In-Reply-To: <9ca9fc34-e5ce-49b4-9733-0a04394c1eee@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1265153145055302052==" List-Id: --===============1265153145055302052== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello *, being in charge of mastering Core Update 182, I've just created the new updat= e, and added most of the pending patches from Patchwork. The latter is not quite complete yet; I strive to be up to speed by the end of this week. As far as package updates are concerned, I'd like to update the following one= s, unless someone else is already working on them: - OpenSSH - strongSwan - Tor In C182, we have a linux-firmware update, which already takes quite some brea= thing room in terms of file size. Unless something urgent comes up, it might be sen= sible to close this update sooner rather than later, so it can go into testing once Core Update 181 is released. Thoughts/comments? Thanks, and best regards, Peter M=C3=BCller > Michael, >=20 > I am back from my holiday trip visiting my family and friends in the UK. >=20 > I will be working again on the OpenVPN package but that won't be ready for = CU182. >=20 > I am currently working through about 20 package updates which should get su= bmitted over the next couple of days. >=20 > I have some minor bug fixes that may get submitted in time for CU182. >=20 > Overall, for CU182, there is nothing critical that I am working on beyond n= ormal package updates, so you can decide form the patches I submit what to us= e and what to leave for a following CU. >=20 >=20 > Regards, >=20 > Adolf. >=20 >=20 > On 07/11/2023 19:22, Peter M=C3=BCller wrote: >> Hello Michael, >> hello *, >> >>> Hello everyone, >>> >>> Since this month=E2=80=99s video conference has been canceled, here is a = couple of updates from my side: >>> >>> * Core Update 181 has been branched yesterday. I have this running in my = office for a little while and it seems to be a solid update. It also has a lo= t of security fixes, so please give it a good test that we can hopefully rele= ase this in two weeks. >> indeed, Core Update 181 seems to work fine without any hiccups whatsoever.= :-) >> >>> * For the following update(s): what do we have in the pipeline? Just to c= oordinate that we don=E2=80=99t have too much in one update :) >> Unless we have more pressing things on our agenda, I remember Adolf saying >> that there are still a couple of packages, particularly libraries, which he >> did not had the resources to work through. At some point, it might be sens= ible >> to have something like a distributed mini-hackathon to ensure that everyth= ing >> we include is at least roughly up to date, and if it's just by slicing the >> package list and distribute the shares. :-) >> >> At some point, I had the idea to keep an eye on various security advisories >> published by other distributions to identify non-prolific packages with >> important updates that might otherwise have flown under our radar, but this >> approach never worked well... >> >> Aside from updating, I recall Stefan working on porting firewall groups to >> ipset a while ago. Perhaps this is something we can then focus on to push >> out of the door next? >> >> Just my two cents. I currently do not have anything major on my docket list >> for IPFire 2.x. :-) >> >> All the best, >> Peter M=C3=BCller --===============1265153145055302052==--