[Bug 2120204] Re: [SRU] MariaDB 11.4.8, 10.11.14, 10.6.23 in all maintained Ubuntu releases

[Timo Aaltonen]

Hello Otto, or anyone else affected,

Accepted mariadb into plucky-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mariadb/1:11.4.8-0ubuntu0.25.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
plucky to verification-done-plucky. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-plucky. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mariadb (Ubuntu Plucky)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-plucky

** Changed in: mariadb (Ubuntu Noble)
       Status: New => Fix Committed

** Tags added: verification-needed-noble

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2120204

Title:
  [SRU] MariaDB 11.4.8, 10.11.14, 10.6.23 in all maintained Ubuntu
  releases

Status in mariadb package in Ubuntu:
  Confirmed
Status in mariadb-10.6 package in Ubuntu:
  Invalid
Status in mariadb source package in Jammy:
  Invalid
Status in mariadb-10.6 source package in Jammy:
  Fix Committed
Status in mariadb source package in Noble:
  Fix Committed
Status in mariadb source package in Plucky:
  Fix Committed

Bug description:
  This issue tracks an update for the MariaDB and Galera packages,
  moving to versions:

  * questing (25.10): MariaDB 1:11.8.3
  * plucky (25.04): MariaDB 1:11.4.8
  * noble (24.04): MariaDB 1:10.11.14
  * jammy (22.04): MariaDB 1:10.6.23

  These minor maintenance releases include bug fixes following the SRU special case documentation at
  https://documentation.ubuntu.com/sru/en/latest/reference/exception-MariaDB-Galera-Updates/.

  Upstream did not announce any new CVEs fixed by this release, so these
  versions will not be uploaded as security updates, but as regular
  stable updates.

  [Upstream changes]

  The new versions, along with descriptions of changes and detailed
  changelogs for each version will be posted as MRs
  https://salsa.debian.org/mariadb-team/mariadb-server/

  So far the 11.8.3 import to Debian unstable (and Ubuntu devel) has
  been posted for review at https://salsa.debian.org/mariadb-
  team/mariadb-server/-/merge_requests/129

  [Test Plan]

  TODO: Check that builds pass on all Ubuntu architectures
  TODO: Check that the full build passed, including checks for file locations,
        symbols file and ABI stability and the post-build upstream tests
  TODO: Check DEP-8 (autopkgtests) pass
  TODO: If that the same update in Debian unstable and Ubuntu devel passed all
        QA systems, including DEP-8 (autopkgtests) for reverse dependencies
  TODO: If there are any non passing tests - explain why that is ok in this case
  TODO: Add results of an autopkgtest run against all the new versions
  TODO: If available, check status of Debian Salsa pipelines

  [Regression Potential]

  The build incorporates an extensive build and integration test suite. The
  upstream also releases their own .deb packages and they too run extensive
  tests on them. Regressions would likely arise from a change in interaction
  with Ubuntu-specific integrations.

  Some regressions were already discovered while preparing
  https://salsa.debian.org/mariadb-team/mariadb-
  server/-/merge_requests/129 and patched to partially revert some
  upstream changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2120204/+subscriptions