From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: CU178 kernel fixes Testing Date: Mon, 14 Aug 2023 18:37:16 +0200 Message-ID: <28abdec8-9e49-4aec-b071-0fada9e443f8@ipfire.org> In-Reply-To: <3E6FBC45-5948-40DC-AE39-C92CBA729BBB@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6807867491397705618==" List-Id: --===============6807867491397705618== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 14/08/2023 17:42, Michael Tremer wrote: > Hello, >=20 > I already bumped these again and copied them manually into the stable branc= h. >=20 > Users should now see those updates. >=20 > But I wasn=E2=80=99t aware of nping=E2=80=A6 I only did these: >=20 > https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommitdiff;h=3D80ff3f08c4= 9fbf0580392a9afda43d99e50d43ba nping is one of the binaries from nmap so the bump of nmap package will=20 cover nping. Regards, Adolf. >=20 > -Michael >=20 >> On 14 Aug 2023, at 15:19, jon wrote: >> >> What about the rebuilds like nmap, monit, nping, etc.?? >> >> Jon Murphy >> jon.murphy(a)ipfire.org >> >> >> >>> On Aug 14, 2023, at 9:03 AM, Michael Tremer = wrote: >>> >>> Hello Adolf, >>> >>>> On 14 Aug 2023, at 12:26, Adolf Belka wrote: >>>> >>>> Hi All, >>>> >>>> >>>> I didn't see any further notification about the kernel fixes in CU178 be= ing available to test but looking in the Changelog in the nightlies it seemed= that the fixes were available in the CU178 version in master. >>> >>> Sorry for the confusion. Arne and I made a quick plan how to move forward= with all those large security issues over the phone. >>> >>> Since I was traveling last week I didn=E2=80=99t have a chance to test th= e update (so that at least a second pair of eyeballs has confirmed that we do= n=E2=80=99t break things really) before the announcement went out. This morni= ng, I installed the update and pretty much immediately pressed the button for= the announcement. >>> >>>> So I have tested it on 2 vm systems that I have. >>>> >>>> After update the systems were on 178 Development Build master/41e33931. = During the reboot on both systems no issues were found and no red warning mes= sages. >>> >>> Very good! >>> >>> We decided to push all those changes straight to the master branch so tha= t we gain more testers quickly and moved c178 to 179 and left that in next. I= n order to be able to release the update as quickly as possible, we didn=E2= =80=99t back port anything else from next into master as we couldn=E2=80=99t = find anything that is *really* urgent. >>> >>>> OpenVPN RW and N2N both worked as normal after the update. >>>> >>>> Ran for a couple of hours and did a range of web activities. >>>> >>>> Everything worked as expected and all graphs reviewed showed data as nor= mally expected. >>>> >>>> >>>> No problems found. >>> >>> That is the stuff I want to hear :) >>> >>> Unless someone reports any new regressions, I would like to release this = update maybe on Wednesday or Thursday. >>> >>> Best, >>> -Michael >>> >>>> >>>> >>>> Regards, >>>> >>>> Adolf. >>>> >>>> >>> >> >=20 --=20 Sent from my laptop --===============6807867491397705618==--