From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: The Upcoming Core Update(s) Date: Tue, 21 Nov 2023 21:50:14 +0100 Message-ID: <14f9200b-e15a-4b9a-8864-6bc0259f216f@ipfire.org> In-Reply-To: <76bf3e38-f21e-4ff7-86a0-0801b0067bca@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2766576664361941723==" List-Id: --===============2766576664361941723== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Peter, On 21/11/2023 21:39, Peter M=C3=BCller wrote: > Hello *, > > being in charge of mastering Core Update 182, I've just created the new upd= ate, > and added most of the pending patches from Patchwork. The latter is not qui= te > 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 o= nes, > unless someone else is already working on them: > > - OpenSSH > - strongSwan I have already built the updated version of strongswan and will submit=20 the patch later this evening. Regards, Adolf > - Tor > > In C182, we have a linux-firmware update, which already takes quite some br= eathing > room in terms of file size. Unless something urgent comes up, it might be s= ensible > to close this update sooner rather than later, so it can go into testing on= ce > Core Update 181 is released. > > Thoughts/comments? > > Thanks, and best regards, > Peter M=C3=BCller > >> Michael, >> >> I am back from my holiday trip visiting my family and friends in the UK. >> >> I will be working again on the OpenVPN package but that won't be ready for= CU182. >> >> I am currently working through about 20 package updates which should get s= ubmitted over the next couple of days. >> >> I have some minor bug fixes that may get submitted in time for CU182. >> >> Overall, for CU182, there is nothing critical that I am working on beyond = normal package updates, so you can decide form the patches I submit what to u= se and what to leave for a following CU. >> >> >> Regards, >> >> Adolf. >> >> >> 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 l= ot of security fixes, so please give it a good test that we can hopefully rel= ease 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 = coordinate 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 sen= sible >>> to have something like a distributed mini-hackathon to ensure that everyt= hing >>> 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 advisori= es >>> published by other distributions to identify non-prolific packages with >>> important updates that might otherwise have flown under our radar, but th= is >>> 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 li= st >>> for IPFire 2.x. :-) >>> >>> All the best, >>> Peter M=C3=BCller --=20 Sent from my laptop --===============2766576664361941723==--