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

[Michael Tremer <michael.tremer@ipfire.org>]

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

Hello,

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

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

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

-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
> 
> - #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/.
> 
> - #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
> 
> 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
>