public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
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	[thread overview]
Message-ID: <d2b18a44-9a40-4dec-b85e-40b05b13389a@ipfire.org> (raw)
In-Reply-To: <D6271D26-31DB-4217-A59E-74C9C7250EEB@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 3350 bytes --]

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(a)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>
> 

  reply	other threads:[~2024-03-25 13:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <171135811429.1850211.10643578824706352392.ipfire@ipfire.org>
2024-03-25 11:10 ` Adolf Belka
2024-03-25 11:12   ` Michael Tremer
2024-03-25 13:09     ` Adolf Belka [this message]
2024-03-25 15:02 ` Adolf Belka
2024-03-25 15:49   ` Nick Howitt
2024-03-25 16:29     ` Adolf Belka
2024-03-26 10:55       ` Michael Tremer
2024-03-26 11:37         ` Adolf Belka
2024-03-26 11:45           ` Michael Tremer
2024-03-26 12:35             ` Adolf Belka
2024-03-26 14:44               ` Michael Tremer
2024-03-27 10:05                 ` Adolf Belka
2024-03-27 10:14                   ` Michael Tremer
2024-03-27 11:25                     ` Adolf Belka
2024-03-26 12:36           ` Nick Howitt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d2b18a44-9a40-4dec-b85e-40b05b13389a@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox