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 together with an update of the samba lfs file to add wsdd as a dependency. Unfortunately it turned out I had provided a single patch with both changes in the 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 change 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 dependency.
Regards,
Adolf.
On 25/03/2024 10:15, IPFire Project wrote:
This update is another testing version for IPFire: It comes with the brand release of the IPFire IPS, a number of bug fixes across the entire system and a good amount of package updates. Test it while it's still hot!
IPFire_
IPFire 2.29 - Core Update 185 is available for testing
This update is another testing version for IPFire: It comes with the brand release of the IPFire IPS, a number of bug fixes across the entire system and a good amount of package updates. Test it while it's still hot!
Read The Full Post On Our Blog https://www.ipfire.org/blog/ipfire-2-29-core-update-185-is-available-for-testing?utm_medium=email&utm_source=blog-announcement
The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
Unsubscribe https://www.ipfire.org/unsubscribe
Hello Adolf,
I also slightly cramp when I see emails regarding to these announcements.
But this isn’t a big problem at all. It is an add-ons so we don’t even have to touch the updater.
-Michael
On 25 Mar 2024, at 11:10, Adolf Belka adolf.belka@ipfire.org 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 together with an update of the samba lfs file to add wsdd as a dependency. Unfortunately it turned out I had provided a single patch with both changes in the 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 change 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 dependency.
Regards,
Adolf.
On 25/03/2024 10:15, IPFire Project wrote:
This update is another testing version for IPFire: It comes with the brand release of the IPFire IPS, a number of bug fixes across the entire system and a good amount of package updates. Test it while it's still hot! IPFire_ IPFire 2.29 - Core Update 185 is available for testing This update is another testing version for IPFire: It comes with the brand release of the IPFire IPS, a number of bug fixes across the entire system and a good amount of package updates. Test it while it's still hot! Read The Full Post On Our Blog https://www.ipfire.org/blog/ipfire-2-29-core-update-185-is-available-for-testing?utm_medium=email&utm_source=blog-announcement The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany Unsubscribe https://www.ipfire.org/unsubscribe
Hi Michael & Stefan,
On 25/03/2024 12:12, Michael Tremer wrote:
Hello Adolf,
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 problem.
I then created a new CU184 vm and added PT Attack into it and selected the rules.
Then I ran the CU185 Testing update and the WUI page basically stuck at the running 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 second 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 earlier. https://bugzilla.ipfire.org/show_bug.cgi?id=13638
Regards,
Adolf.
But this isn’t a big problem at all. It is an add-ons so we don’t even have to touch the updater.
-Michael
On 25 Mar 2024, at 11:10, Adolf Belka adolf.belka@ipfire.org 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 together with an update of the samba lfs file to add wsdd as a dependency. Unfortunately it turned out I had provided a single patch with both changes in the 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 change 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 dependency.
Regards,
Adolf.
On 25/03/2024 10:15, IPFire Project wrote:
This update is another testing version for IPFire: It comes with the brand release of the IPFire IPS, a number of bug fixes across the entire system and a good amount of package updates. Test it while it's still hot! IPFire_ IPFire 2.29 - Core Update 185 is available for testing This update is another testing version for IPFire: It comes with the brand release of the IPFire IPS, a number of bug fixes across the entire system and a good amount of package updates. Test it while it's still hot! Read The Full Post On Our Blog https://www.ipfire.org/blog/ipfire-2-29-core-update-185-is-available-for-testing?utm_medium=email&utm_source=blog-announcement The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany Unsubscribe https://www.ipfire.org/unsubscribe
-
Adolf Belka -
Michael Tremer