Hi release team,

The MR https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/98
has been reviewed (thanks Sylvain) and I think it is ready to be
uploaded to stable-proposed-updates.

I've attached the output `git diff debian/1%10.11.9-0+deb12u1 --
debian > debian-1%10.11.9-0+deb12u1.diff`.

As there are quite a few changes, they may need additional
justification on why they are all indeed necessary bugfixes, and also
how their quality has been assured:

- Upstream MariaDB is a large project and cherry-picking only security
fixes is not feasible. As we skipped 10.11.10, this has now changes
from two upstream maintenance releases.

- Upstream releases included fixes in the Debian packaging. Debian
should also include these changes to avoid deviating from upstream.
They are relatively safe to include, as upstream has already published
them and there are no reported regressions.

- Several users in Debian reported service restart issues that have
been fixed in unstable for a long time, and those fixes have proven to
be correct. These fixes should also be included in the stable update,
and were indeed proposed during the Bookworm freeze, but the fixes
were new at the time and at the time not proven, so they were left out
of Bookworm. Currently Debian users are not reporting this, but we can
see that the equivalent Ubuntu 24.04 version has multiple apport
reports about the same issue, and it is likely Debian users are also
affected.

- All the changes in this release have already shipped in MariaDB
11.4.5 in Debian unstable, and no regressions have been reported so
far.

- The updates have been tested with an extensive Bookworm-specific
Salsa CI pipeline that includes multiple install/upgrade scenarios
that are relevant for this package with a service and presistent data.
Some of the changes are purely related to testing. They are not
strictly necessary for Bookworm itself, but they help keep the Salsa
CI pipeline fully green, thus indirectly help ensure that any future
regressions in Bookworm uploads can be easily detected.

- One README update is included as some users reported issues with
accessing their database as root user, which is a severe usability
issue and the README update will mitigate it.

- One patch of low importance was dropped as rewriting the patch is
riskier than just dropping it and aligning with upstream changes in
the domain. Other patches were refreshed to make future upstream
imports easier, even though refreshing patches isn't strictly
necessary for a single Bookworm update.

Let me know if you have further questions.

Also note that the sooner this can be uploaded to
stable-updates-proposed, the more time we will have to collect
build/test/user feedback and potentially catch any potential
regressions before the next point release in actual stable-updates.

Thanks!

Attachment: debian-1%10.11.9-0+deb12u1.diff.xz
Description: application/xz

Reply via email to