From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: IPFire 2.29 - Core Update 185 is available for testing Date: Mon, 25 Mar 2024 14:09:27 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0995528437557604042==" List-Id: --===============0995528437557604042== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael & Stefan, On 25/03/2024 12:12, Michael Tremer wrote: > Hello Adolf, >=20 > I also slightly cramp when I see emails regarding to these announcements. Sorry for causing you that feeling. Unfortunately, this next issue may require bigger changes. Doing an upgrade with my existing suricata providers worked without any probl= em. I then created a new CU184 vm and added PT Attack into it and selected the ru= les. Then I ran the CU185 Testing update and the WUI page basically stuck at the r= unning the CU185 and post scripts section. I checked via the console and the update had completed with no errors in the = update logfile. However the WUI page fails to connect. It times out. I tried this twice more with and without PT Attack in the suricata providers.= Whenever P Attack was included the WUI page stops functioning. Then on a vm that was timing out for the WUI page I stopped suricata via the = console. The WUI page then became accessible again. I have tested this a seco= nd time and confirmed that a non responding WUI becomes responding again when= suricata is stopped. I have no idea what is causing the problem but I have been able to reproduce = it several times now with my vm systems. I will add this info into the Suricata bug that has been raised by Michael ea= rlier. https://bugzilla.ipfire.org/show_bug.cgi?id=3D13638 Regards, Adolf. >=20 > But this isn=E2=80=99t a big problem at all. It is an add-ons so we don=E2= =80=99t even have to touch the updater. >=20 > -Michael >=20 >> On 25 Mar 2024, at 11:10, Adolf Belka wrote: >> >> Hi Michael, >> >> First issue found. Due to a boo-boo made by me related to wsdd. >> >> I had submitted what I thought was a patch set for the samba initscript to= gether with an update of the samba lfs file to add wsdd as a dependency. Unfo= rtunately it turned out I had provided a single patch with both changes in th= e same patch >> >> You raised the question about not having the samba initscript calling the = wsdd initscript. I updated that script and submitted it but thought the chang= e of adding the wsdd as a dependency had been merged so did not send a v2 of = that change. >> >> So wsdd is not getting installed when samba is being updated. >> >> I will submit a new patch for the samba lfs update to add wsdd as a depend= ency. >> >> Regards, >> >> Adolf. >> >> >> On 25/03/2024 10:15, IPFire Project wrote: >>> This update is another testing version for IPFire: It comes with the bran= d release of the IPFire IPS, a number of bug fixes across the entire system a= nd a good amount of package updates. Test it while it's still hot! >>> =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= =80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C = =E2=80=8C =E2=80=8C =E2=80=8C >>> IPFire_ >>> IPFire 2.29 - Core Update 185 is available for testing >>> This update is another testing version for IPFire: It comes with the bran= d release of the IPFire IPS, a number of bug fixes across the entire system a= nd a good amount of package updates. Test it while it's still hot! >>> Read The Full Post On Our Blog >>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstra=C3=9Fe 8, 4= 5711 Datteln, Germany >>> Unsubscribe >=20 --===============0995528437557604042==--