From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.27 - Core Update 170 is available for testing
Date: Mon, 22 Aug 2022 20:36:49 +0000
Message-ID: <23865b0b-74b7-0a5d-a1d7-76e0a68ad65e@ipfire.org>
In-Reply-To: <dd9c9289-339d-b53f-75bf-05b6ebd26541@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2832472787023599023=="
List-Id: <development.lists.ipfire.org>

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

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 upda=
te:

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

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

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

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 d=
eveloped
until then.

As always, comments/questions/complaints are appreciated.

Best,
Peter M=C3=BCller


--===============2832472787023599023==--