Re: IPFire 2.27 - Core Update 170 is available for testing

["Peter Müller" <peter.mueller@ipfire.org>]

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

Hello Michael,

> Hello,
> 
> I just wanted to reach out and hear if there is any more feedback on this update.

nothing from my end. The update runs fine on my physical testing machine since two weeks.

> Lots of people have been away, and so it was *very* quiet in the last few weeks.

Yes, I kind of have a bad conscience for being away again next week, but it can't be helped.

> I don’t feel confident at all about this update, yet. Anyone who can take concern away from me?

See below.

> 
> -Michael
> 
>> On 22 Aug 2022, at 21:36, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>
>> Hello *,
>>
>> thank you all for the testing of Core Update 170, and the robust reporting!
>>
>> From what I gathered, there are currently three bugs unresolved in this update:
>>
>> - #12916 (messagebus: multiple "/etc/rc.d/init.d/functions: line 332: shift: 2: shift count out of range")
>> 	=> Affects people having installed the "dbus" add-on

Patch merged into "next".

>>
>> - #12917 (When enabling ipblocklist WUI page a blank screen is shown)
>> 	=> Hopefully fixed by https://patchwork.ipfire.org/project/ipfire/patch/06825b38-ec53-38c5-c8ce-12d70c1acb5b(a)ipfire.org/.

Submitted a version 3 that is hopefully finally fine.

>>
>> - #12918 (When running a fuse mount for borgbackup get error message "fuse: device not found, try 'modprobe fuse' first")
>> 	=> Might be a local testing issue, not a general problem with the Core Update

Turned out to be a local issue indeed.

Two additional bugs crept up recently (indicating to me that there _is_ some testing audience):

- #12919 (IPSec/alias-IP failure)
	=> Not sure if this should be considered a show-stopper, waiting for user feedback

- #12924 (Cannot access https web pages in CUPS)
	=> Currently unassigned, root cause under investigation

Since no really severe bugs or user complaints arose, I would consider C170 to be free of major
surprises/disappointments. #12917 obviously needs to be fixed before a release, and #12919 should
be, AFAIK. I would not consider #12924 to be a show-stopper.

Hopes this clarifies the situation a bit. :-)

Thanks, and best regards,
Peter Müller

>>
>> For an update of this size and changes, that strikes me as a rather short list
>> of bugs, so it may either be that we are all really overlooking something, or it
>> is just a pretty solid Core Update. :-)
>>
>> Due to my current workload situation, I would like to give C170 another ~ two weeks,
>> and would aim for a release around September 2nd or 3rd. Given the currently
>> unresolved bugs, I think the time is sufficient to have any missing patches developed
>> until then.
>>
>> As always, comments/questions/complaints are appreciated.
>>
>> Best,
>> Peter Müller
>>
>