public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <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	[thread overview]
Message-ID: <23865b0b-74b7-0a5d-a1d7-76e0a68ad65e@ipfire.org> (raw)
In-Reply-To: <dd9c9289-339d-b53f-75bf-05b6ebd26541@ipfire.org>

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

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


  reply	other threads:[~2022-08-22 20:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166057920894.3662646.17671924655074704229.ipfire@ipfire.org>
2022-08-16 13:58 ` Adolf Belka
2022-08-16 14:36   ` Adolf Belka
2022-08-18 16:47     ` Adolf Belka
2022-08-19  8:46   ` Michael Tremer
2022-08-19  9:12     ` Peter Müller
2022-08-19  9:35       ` Adolf Belka
2022-08-19  8:47   ` Michael Tremer
2022-08-19  9:33     ` Adolf Belka
2022-08-19  9:54       ` Adolf Belka
2022-08-19 10:09         ` Adolf Belka
2022-08-22 20:36           ` Peter Müller [this message]
2022-09-01 15:02             ` Michael Tremer
2022-09-01 20:51               ` Peter Müller

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=23865b0b-74b7-0a5d-a1d7-76e0a68ad65e@ipfire.org \
    --to=peter.mueller@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