From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.27 - Core Update 170 is available for testing
Date: Thu, 01 Sep 2022 16:02:50 +0100
Message-ID: <AE831CA8-DCB7-4F3C-B535-A3652925C05D@ipfire.org>
In-Reply-To: <23865b0b-74b7-0a5d-a1d7-76e0a68ad65e@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4843906044055450596=="
List-Id: <development.lists.ipfire.org>

--===============4843906044055450596==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello,

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

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

I don=E2=80=99t 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=C3=BCller <peter.mueller(a)ipfire.org> wr=
ote:
>=20
> Hello *,
>=20
> thank you all for the testing of Core Update 170, and the robust reporting!
>=20
> From what I gathered, there are currently three bugs unresolved in this upd=
ate:
>=20
> - #12916 (messagebus: multiple "/etc/rc.d/init.d/functions: line 332: shift=
: 2: shift count out of range")
> 	=3D> Affects people having installed the "dbus" add-on
>=20
> - #12917 (When enabling ipblocklist WUI page a blank screen is shown)
> 	=3D> Hopefully fixed by https://patchwork.ipfire.org/project/ipfire/patch/=
06825b38-ec53-38c5-c8ce-12d70c1acb5b(a)ipfire.org/.
>=20
> - #12918 (When running a fuse mount for borgbackup get error message "fuse:=
 device not found, try 'modprobe fuse' first")
> 	=3D> Might be a local testing issue, not a general problem with the Core U=
pdate
>=20
> For an update of this size and changes, that strikes me as a rather short l=
ist
> of bugs, so it may either be that we are all really overlooking something, =
or it
> is just a pretty solid Core Update. :-)
>=20
> Due to my current workload situation, I would like to give C170 another ~ t=
wo 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.
>=20
> As always, comments/questions/complaints are appreciated.
>=20
> Best,
> Peter M=C3=BCller
>=20


--===============4843906044055450596==--