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

[Otto Kekäläinen]

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.

[Otto Kekäläinen (otto)]

Merge Requests are now available and awaiting review from a second person at

* https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/133: plucky (25.04): MariaDB 1:11.4.8
* https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/134: noble (24.04): MariaDB 1:10.11.14
* https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/135: jammy (22.04): MariaDB 1:10.6.23

The CI and MR description explains how all of these are fulfilled:

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

[Otto Kekäläinen (otto)]

According to the documented process (https://documentation.ubuntu.com/sru/en/latest/) next step is to upload to the respective Upload queues:

* https://launchpad.net/ubuntu/plucky/+queue
* https://launchpad.net/ubuntu/noble/+queue
* https://launchpad.net/ubuntu/jammy/+queue

However, I am asking reaching out to https://matrix.to/#/#sru:ubuntu.com and asking for review already pre-upload as the MRs posted above are likely much easier to review than looking at the upload queues.

[Otto Kekäläinen (otto)]

As per process in https://documentation.ubuntu.com/sru/en/latest/explanation/further-requirements/#newer-releases the Plucky upload is no longer required as Questing was released.

[Otto Kekäläinen (otto)]

The "Ubuntu Sponsors" has been subscribed for over a month now but no sponsor attended this yet.

[Lena Voytek (lvoytek)]

It seems a lot of updates are falling through the cracks when it comes to sponsorships. I'll take this one

[Otto Kekäläinen (otto)]

Pending in queues at:

- https://launchpad.net/ubuntu/plucky/+queue?queue_state=1
- https://launchpad.net/ubuntu/noble/+queue?queue_state=1
- https://launchpad.net/ubuntu/jammy/+queue?queue_state=1

[Timo Aaltonen (tjaalton)]

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.

[Timo Aaltonen (tjaalton)]

Hello Otto, or anyone else affected,

Accepted mariadb into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mariadb/1:10.11.14-0ubuntu0.24.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-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. 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.

[Timo Aaltonen (tjaalton)]

Hello Otto, or anyone else affected,

Accepted mariadb-10.6 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mariadb-10.6/1:10.6.23-0ubuntu0.22.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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Otto Kekäläinen (otto)]

# Verification of https://launchpad.net/ubuntu/+source/mariadb-10.6/1:10.6.23-0ubuntu0.22.04.1

✔ https://launchpad.net/ubuntu/+source/mariadb-10.6/1:10.6.23-0ubuntu0.22.04.1 built on all architectures

✔ Upgrades successfully when -proposed enabled

Exact steps to test upgrades in -proposed for this package that includes a running service inside a container:

```
apt update && apt install --yes lsb-release
# Enable automatic restarts from maint scripts
sed -i "s/101/0/g" /usr/sbin/policy-rc.d
# Fake /sbin/runlevel to avoid warnings of "invoke-rc.d: could not determine current runlevel"
echo -e '#!/bin/sh\necho "N 5"' > /sbin/runlevel; chmod +x /sbin/runlevel

apt install --yes mariadb-server
mariadb -e "SELECT version()"

cat <<EOF > /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list
# Enable Ubuntu proposed archive
deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe
EOF
apt update
apt upgrade --yes
mariadb -e "SELECT version()"
```

Result:
```
# mariadb -e "SELECT version()"
+----------------------------------+
| version() |
+----------------------------------+
| 10.6.23-MariaDB-0ubuntu0.22.04.1 |
+----------------------------------+
```

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted mariadb-10.6 (1:10.6.23-0ubuntu0.22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

dbconfig-common/2.0.21 (armhf)
mariadb-10.6/1:10.6.23-0ubuntu0.22.04.1 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#mariadb-10.6

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Otto Kekäläinen (otto)]

# Verification of https://launchpad.net/ubuntu/+source/mariadb/1:10.11.14-0ubuntu0.24.04.1

🗙 https://launchpad.net/ubuntu/+source/mariadb/1:10.11.14-0ubuntu0.24.04.1 build for amd64 failed

There is no log, so apparently the builder itself failed to start the job? There is not restart button visible, not at least for me, so I can't try rebuilding it.

[Otto Kekäläinen (otto)]

# Verification of https://launchpad.net/ubuntu/+source/mariadb/1:11.4.8-0ubuntu0.25.04.1

🗙 https://launchpad.net/ubuntu/+source/mariadb/1:11.4.8-0ubuntu0.25.04.1 builds for armhf and ppc64el failed

There is no log, so apparently the builder itself failed to start the job? There is not restart button visible, not at least for me, so I can't try rebuilding it.

✔ Upgrades successfully when -proposed enabled

Exact steps to test upgrades in -proposed for this package that includes a running service inside a container:

```
apt update && apt install --yes lsb-release
# Enable automatic restarts from maint scripts
sed -i "s/101/0/g" /usr/sbin/policy-rc.d
# Fake /sbin/runlevel to avoid warnings of "invoke-rc.d: could not determine current runlevel"
echo -e '#!/bin/sh\necho "N 5"' > /sbin/runlevel; chmod +x /sbin/runlevel

apt install --yes mariadb-server
mariadb -e "SELECT version()"

cat <<EOF > /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list
# Enable Ubuntu proposed archive
deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe
EOF
cat <<EOF >/etc/apt/preferences.d/proposed-updates
# Configure apt to allow selective installs of packages from proposed
Package: *
Pin: release a=$(lsb_release -cs)-proposed
Pin-Priority: 800
EOF
apt update
apt upgrade --yes
mariadb -e "SELECT version()"
```

Result:
```
+---------------------------------+
| version() |
+---------------------------------+
| 11.4.8-MariaDB-0ubuntu0.25.04.1 |
+---------------------------------+
```

Note, that unlike on Jammy, on Plucy one needs to pin -proposed for updates to actually get selected. Also using the pinning documented at https://wiki.ubuntu.com/Testing/EnableProposed isn't enough, but one needs to set priority to e.g. '800' for the packages to be selected for upgrade.

[Otto Kekäläinen (otto)]

Reviewing autopkgtest logs of:

dbconfig-common/2.0.21 (armhf)

240s autopkgtest [15:09:12]: test command1: -----------------------]
245s command1 PASS

548s autopkgtest [15:14:20]: test command2: -----------------------]
553s command2 PASS

849s autopkgtest [15:19:21]: test command3: - - - - - - - - - - results - - - - - - - - - -
849s command3 PASS

Later in the log there are some failures, perhaps due to testbed?

```
1032s Setting up postgresql-common (238) ...
1032s ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
1032s Adding user postgres to group ssl-cert
1032s
1032s Creating config file /etc/postgresql-common/createcluster.conf with new version
1032s Building PostgreSQL dictionaries from installed myspell/hunspell packages...
1032s Removing obsolete dictionary files:
1033s Created symlink /etc/systemd/system/multi-user.target.wants/postgresql.service → /lib/systemd/system/postgresql.service.
1033s Setting up libdbd-mysql-perl:armhf (4.050-5ubuntu0.22.04.1) ...
1033s Setting up mysql-server-core-8.0 (8.0.44-0ubuntu0.22.04.1) ...
1033s Setting up dbconfig-sqlite3 (2.0.21) ...
1033s Setting up dh-strip-nondeterminism (1.13.0-1) ...
1033s Setting up gcc-11 (11.4.0-1ubuntu1~22.04.2) ...
1033s Setting up cpp (4:11.2.0-1ubuntu1) ...
1033s Setting up libc6-dev:armhf (2.35-0ubuntu3.11) ...
1033s Setting up postgresql-14 (14.20-0ubuntu0.22.04.1) ...
1033s Creating new PostgreSQL cluster 14/main ...
1033s /usr/lib/postgresql/14/bin/initdb -D /var/lib/postgresql/14/main --auth-local peer --auth-host scram-sha-256 --no-instructions
1033s The files belonging to this database system will be owned by user "postgres".
1033s This user must also own the server process.
1033s
1033s The database cluster will be initialized with locale "C.UTF-8".
1033s The default database encoding has accordingly been set to "UTF8".
1033s The default text search configuration will be set to "english".
1033s
1033s Data page checksums are disabled.
1033s
1033s fixing permissions on existing directory /var/lib/postgresql/14/main ... ok
1033s creating subdirectories ... ok
1033s selecting dynamic shared memory implementation ... posix
1033s selecting default max_connections ... 100
1033s selecting default shared_buffers ... 128MB
1033s selecting default time zone ... Etc/UTC
1033s creating configuration files ... ok
1034s running bootstrap script ... ok
1034s performing post-bootstrap initialization ... ok
1034s syncing data to disk ... ok
1035s update-alternatives: using /usr/share/postgresql/14/man/man1/postmaster.1.gz to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode
1037s Setting up mysql-server-8.0 (8.0.44-0ubuntu0.22.04.1) ...
1037s update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode
1038s Renaming removed key_buffer and myisam-recover options (if present)
1046s mysqld will log errors to /var/log/mysql/error.log
1046s mysqld is running as pid 2866
1051s apparmor_parser: Unable to replace "/usr/sbin/mysqld". Permission denied; attempted to load a profile while confined?
1051s Created sym...

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted mariadb (1:11.4.8-0ubuntu0.25.04.1) for plucky have finished running.
The following regressions have been reported in tests triggered by the package:

libdbd-mariadb-perl/1.22-1ubuntu1 (arm64)
mariadb-connector-odbc/3.1.15-3 (s390x)
mediawiki-extension-youtube/1.9.3~git20221020.e005c0b-1ubuntu1 (amd64)
mediawiki-skin-greystuff/1.2.5~git20220922.60bda8c-2ubuntu1 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/plucky/update_excuses.html#mariadb

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Otto Kekäläinen (otto)]

Reviewing autopkgtest logs:

libdbd-mariadb-perl/1.22-1ubuntu1 (arm64)

153s autopkgtest [16:39:43]: test pkg-perl-autopkgtest-build-deps-mariadb: -----------------------]
155s autopkgtest [16:39:45]: test pkg-perl-autopkgtest-build-deps-mariadb: - - - - - - - - - - results - - - - - - - - - -
155s pkg-perl-autopkgtest-build-deps-mariadb PASS
...
243s Investigating (0) mysql-server:arm64 < none -> 8.4.7-0ubuntu0.25.04.2 @un puN Ib >
243s Broken mysql-server:arm64 Conflicts on mariadb-common:arm64 < none -> 1:11.4.8-0ubuntu0.25.04.1 @un puN >
243s Considering mariadb-common:arm64 -1 as a solution to mysql-server:arm64 0
243s Conflicts//Breaks against version 1:11.4.7-0ubuntu0.25.04.1 for mariadb-common but that is not InstVer, ignoring
243s Conflicts//Breaks against version 1:11.4.5-1 for mariadb-common but that is not InstVer, ignoring
243s Done
243s Some packages could not be installed. This may mean that you have
243s requested an impossible situation or if you are using the unstable
243s distribution that some required packages have not yet been created
243s or been moved out of Incoming.
243s The following information may help to resolve the situation:
243s
243s The following packages have unmet dependencies:
244s mysql-server : Conflicts: mariadb-common but 1:11.4.8-0ubuntu0.25.04.1 is to be installed
244s E: Unable to correct problems, you have held broken packages.
...
595s ERROR (CommandError): No server with a name or ID of '866047de-09d2-41df-bd79-1678a5f184d7' exists.
595s ---------------------------------------------------
595s ------- nova show 866047de-09d2-41df-bd79-1678a5f184d7 (adt-plucky-arm64-libdbd-mariadb-perl-20251205-150806-juju-7f2275-prod-proposed-migration-environment-2-30027a06-26ce-4d00-b0bf-2678e12f2c82) ------
597s ERROR (CommandError): No server with a name or ID of '866047de-09d2-41df-bd79-1678a5f184d7' exists.
597s ---------------------------------------------------
993s sudo-rs: '/tmp/autopkgtest-run-wrapper': command not found
997s <VirtSubproc>: failure: failed to run setup script '/home/ubuntu/autopkgtest/ssh-setup/nova' with command 'revert'
998s autopkgtest [16:53:48]: ERROR: testbed failure: eof from the virtualisation server

While there seems to be something going on with the testbed, there is also a genuine looking conflict "mysql-server : Conflicts: mariadb-common". Oddly this is only visible on the arm64 autopkgtest, not on any other platform. Also this MariaDB update didn't include any debian/control file changes, so it can't be the source of such a package conflict.

mariadb-connector-odbc/3.1.15-3 (s390x)

 55s Setting up mariadb-client-core (1:11.4.8-0ubuntu0.25.04.1) ...
 55s Setting up odbc-mariadb (3.1.15-3) ...
 55s odbcinst: Driver installed. Usage count increased to 1.
 55s Target directory is /etc
 55s Setting up mariadb-server-core (1:11.4.8-0ubuntu0.25.04.1) ...
 55s Setting up mariadb-client (1:11.4.8-0ubuntu0.25.04.1) ...
 55s Setting up mariadb-server (1:11.4.8-0ubuntu0.25.04.1) ...
 56s Created symlink '/etc/systemd/system/multi-user.target.wants/mariadb.service' → '/usr/lib/systemd/system/mariadb.service'.

 58s Processing triggers for man-db (2.13.0-1) ...
 58s Proc...

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted mariadb (1:10.11.14-0ubuntu0.24.04.1) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

libdbd-mysql-perl/4.052-1ubuntu3 (armhf)
mediawiki-skin-greystuff/1.2.5~git20220922.60bda8c-2 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#mariadb

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Otto Kekäläinen (otto)]

# Re-verification of https://launchpad.net/ubuntu/+source/mariadb/1:11.4.8-0ubuntu0.25.04.1

✔ https://launchpad.net/ubuntu/+source/mariadb/1:11.4.8-0ubuntu0.25.04.1 after triggering rebuilds everything passed

# Re-verification of https://launchpad.net/ubuntu/+source/mariadb/1:10.11.14-0ubuntu0.24.04.1

✔ https://launchpad.net/ubuntu/+source/mariadb/1:10.11.14-0ubuntu0.24.04.1 after triggering rebuilds everything passed

✔ Upgrades successfully when -proposed enabled

Exact steps to test upgrades in -proposed for this package that includes a running service inside a container:

```
apt update && apt install --yes lsb-release
# Enable automatic restarts from maint scripts
sed -i "s/101/0/g" /usr/sbin/policy-rc.d
# Fake /sbin/runlevel to avoid warnings of "invoke-rc.d: could not determine current runlevel"
echo -e '#!/bin/sh\necho "N 5"' > /sbin/runlevel; chmod +x /sbin/runlevel

apt install --yes mariadb-server
mariadb -e "SELECT version()"

cat <<EOF > /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list
# Enable Ubuntu proposed archive
deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe
EOF
cat <<EOF >/etc/apt/preferences.d/proposed-updates
# Configure apt to allow selective installs of packages from proposed
Package: *
Pin: release a=$(lsb_release -cs)-proposed
Pin-Priority: 800
EOF
apt update
apt upgrade --yes
mariadb -e "SELECT version()"
```

Result:
```
# mariadb -e "SELECT version()"
+-----------------------------------+
| version() |
+-----------------------------------+
| 10.11.14-MariaDB-0ubuntu0.24.04.1 |
+-----------------------------------+
```

[Otto Kekäläinen (otto)]

As none of the autopkgtest failures look like genuine regressions, I will not do any further actions on them (following https://documentation.ubuntu.com/project/SRU/howto/autopkgtest-failure/ and https://documentation.ubuntu.com/project/SRU/howto/regression/#howto-report-regression).

Also, I see that autopkgtest failures disappeared both from https://ubuntu-archive-team.ubuntu.com/proposed-migration/noble/update_excuses.html#mariadb and https://ubuntu-archive-team.ubuntu.com/proposed-migration/plucky/update_excuses.html#mariadb, probably due to automatic re-running of the tests?

Autopkgtest failures on armhf are still visible at https://ubuntu-archive-team.ubuntu.com/proposed-migration/jammy/update_excuses.html#mariadb-10.6 but they are also likely to disappear if tests re-run based on the investigations above.

[Skia (skia)]

This seems to be well in hands, I'm unsubscribing ubuntu-sponsors

[Andreas Hasenack (ahasenack)]

The autopkgtests look clean now, indeed. The reason this update wasn't released yet, though, is because it doesn't show as green in the SRU pending report[1], and that's because the verification tags are still stating that the verification needs to be done ;)

Otto, I see comments from you doing the verification, would you mind to, if the verification indeed passed, flip the corresponding verification tags to "verification-done-$release"?

1. https://ubuntu-archive-team.ubuntu.com/pending-sru.html

[Otto Kekäläinen (otto)]

Thanks Andreas for following up! I tought this was already approved and uploaded. The docs https://documentation.ubuntu.com/project/SRU/explanation/pipeline/ and elsewhere does not mention anything about "verification tags".

I now removed from this bug reports all tags it had ("verification-needed-jammy verification-needed-noble verification-needed-plucky verification-needed").

[Andreas Hasenack (ahasenack)]

> elsewhere does not mention anything about "verification tags".

The accept comment has the more detailed instructions:

"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."

We don't do releases on fridays, so monday is the next window. Do you have particular interest or urgency in seeing this in plucky still? Because it reached EOL yesterday, and in fact I'm cleaning up the plucky-proposed queue.

[Otto Kekäläinen (otto)]

Thanks for pointing out, indeed the test is there. I guess my brain didn't process it properly as the sentence starts "If this package fixes the bug for you,.." and the tag rename is a the end and the significant part of the tags is in the middle.

Also in this I don't know what "N.B." means, and it isn't explicit on *who* should do the verification, what is verified beyond what the person preparing the update already verified, and that this check depends on these specific tags:

"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."

Once I have my first SRU done end-to-end I will try to contribute by submitting documentation updates to explain the parts that are not omitted from the docs.

And yes you can skip plucky. Just a pity there is so much work and process required from volunteers and then some of the work ends up being done in vain :(

[Andreas Hasenack (ahasenack)]

I know you care deeply about mariadb, that's why I this time didn't skip it in my shift and decided to check if it was really unverified still, and that's when I saw the missing tag. Sorry about plucky, and thanks for still being here.

[Andreas Hasenack (ahasenack)]

I'll go over the other releases on monday.

[Andreas Hasenack (ahasenack)]

$ ./sru-remove -s plucky --reason=eol -p mariadb
Removing packages from plucky-proposed:
 mariadb 1:11.4.8-0ubuntu0.25.04.1 in plucky
  libmariadb-dev 1:11.4.8-0ubuntu0.25.04.1 in plucky amd64
  libmariadb-dev 1:11.4.8-0ubuntu0.25.04.1 in plucky arm64
  libmariadb-dev 1:11.4.8-0ubuntu0.25.04.1 in plucky armhf
  libmariadb-dev 1:11.4.8-0ubuntu0.25.04.1 in plucky ppc64el
  libmariadb-dev 1:11.4.8-0ubuntu0.25.04.1 in plucky riscv64
  libmariadb-dev 1:11.4.8-0ubuntu0.25.04.1 in plucky s390x
  libmariadb-dev-compat 1:11.4.8-0ubuntu0.25.04.1 in plucky amd64
  libmariadb-dev-compat 1:11.4.8-0ubuntu0.25.04.1 in plucky arm64
  libmariadb-dev-compat 1:11.4.8-0ubuntu0.25.04.1 in plucky armhf
  libmariadb-dev-compat 1:11.4.8-0ubuntu0.25.04.1 in plucky ppc64el
  libmariadb-dev-compat 1:11.4.8-0ubuntu0.25.04.1 in plucky riscv64
  libmariadb-dev-compat 1:11.4.8-0ubuntu0.25.04.1 in plucky s390x
  libmariadb3 1:11.4.8-0ubuntu0.25.04.1 in plucky amd64
  libmariadb3 1:11.4.8-0ubuntu0.25.04.1 in plucky arm64
  libmariadb3 1:11.4.8-0ubuntu0.25.04.1 in plucky armhf
  libmariadb3 1:11.4.8-0ubuntu0.25.04.1 in plucky ppc64el
  libmariadb3 1:11.4.8-0ubuntu0.25.04.1 in plucky riscv64
  libmariadb3 1:11.4.8-0ubuntu0.25.04.1 in plucky s390x
  libmariadbd-dev 1:11.4.8-0ubuntu0.25.04.1 in plucky amd64
  libmariadbd-dev 1:11.4.8-0ubuntu0.25.04.1 in plucky arm64
  libmariadbd-dev 1:11.4.8-0ubuntu0.25.04.1 in plucky armhf
  libmariadbd-dev 1:11.4.8-0ubuntu0.25.04.1 in plucky ppc64el
  libmariadbd-dev 1:11.4.8-0ubuntu0.25.04.1 in plucky riscv64
  libmariadbd-dev 1:11.4.8-0ubuntu0.25.04.1 in plucky s390x
  libmariadbd19t64 1:11.4.8-0ubuntu0.25.04.1 in plucky amd64
  libmariadbd19t64 1:11.4.8-0ubuntu0.25.04.1 in plucky arm64
  libmariadbd19t64 1:11.4.8-0ubuntu0.25.04.1 in plucky armhf
  libmariadbd19t64 1:11.4.8-0ubuntu0.25.04.1 in plucky ppc64el
  libmariadbd19t64 1:11.4.8-0ubuntu0.25.04.1 in plucky riscv64
  libmariadbd19t64 1:11.4.8-0ubuntu0.25.04.1 in plucky s390x
  mariadb-backup 1:11.4.8-0ubuntu0.25.04.1 in plucky amd64
  mariadb-backup 1:11.4.8-0ubuntu0.25.04.1 in plucky arm64
  mariadb-backup 1:11.4.8-0ubuntu0.25.04.1 in plucky armhf
  mariadb-backup 1:11.4.8-0ubuntu0.25.04.1 in plucky ppc64el
  mariadb-backup 1:11.4.8-0ubuntu0.25.04.1 in plucky riscv64
  mariadb-backup 1:11.4.8-0ubuntu0.25.04.1 in plucky s390x
  mariadb-client 1:11.4.8-0ubuntu0.25.04.1 in plucky amd64
  mariadb-client 1:11.4.8-0ubuntu0.25.04.1 in plucky arm64
  mariadb-client 1:11.4.8-0ubuntu0.25.04.1 in plucky armhf
  mariadb-client 1:11.4.8-0ubuntu0.25.04.1 in plucky ppc64el
  mariadb-client 1:11.4.8-0ubuntu0.25.04.1 in plucky riscv64
  mariadb-client 1:11.4.8-0ubuntu0.25.04.1 in plucky s390x
  mariadb-client-compat 1:11.4.8-0ubuntu0.25.04.1 in plucky amd64
  mariadb-client-compat 1:11.4.8-0ubuntu0.25.04.1 in plucky arm64
  mariadb-client-compat 1:11.4.8-0ubuntu0.25.04.1 in plucky armhf
  mariadb-client-compat 1:11.4.8-0ubuntu0.25.04.1 in plucky i386
  mariadb-client-compat 1:11.4.8-0ubuntu0.25.04.1 in plucky ppc64el
  mariadb-client-compat 1:11.4.8-0ubuntu0.25.04.1 in plucky riscv64
  mariadb-client-compat 1:11.4.8-0ubuntu0.25.04.1 in plucky s390x
  mariadb-client-core 1:11.4.8-0ubuntu0.25.04.1 in pl...

[Otto Kekäläinen (otto)]

Both updates are green now in https://ubuntu-archive-team.ubuntu.com/pending-sru.html and they have been in proposed way more than 7 days. Is some additional manual action required? By who?

[Julian Andres Klode (juliank)]

The verification of the Stable Release Update for mariadb has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package mariadb - 1:10.11.14-0ubuntu0.24.04.1

---------------
mariadb (1:10.11.14-0ubuntu0.24.04.1) noble; urgency=medium

  * New upstream maintenance release 10.11.14. For details about fixes please
    see https://mariadb.com/docs/release-notes/community-server/10.11/10.11.14
    (LP: #2120204)
  * Drop Hurd patch that is now included upstream
  * Suppress native AIO warning introduced in upstream a87bb96
  * Update server trace to include new parameters and values
  * Update Lintian overrides for new files in latest upstream version
  * Remove obsolete cleanup as upstream moved pam_mariadb_mtr.so in c05b1fe
  * Add debian/source/local-options to suppress WolfSSL line ending errors

  [ Sergei Golubchik ]
  * MDEV-36815 Fresh MariaDB 11.4 installation gives errors when configuring
    utf8

 -- Otto Kekäläinen <email address hidden> Fri, 10 Oct 2025 19:08:29 -0700

[Launchpad Janitor (janitor)]

This bug was fixed in the package mariadb-10.6 - 1:10.6.23-0ubuntu0.22.04.1

---------------
mariadb-10.6 (1:10.6.23-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream maintenance release 10.6.23. For details about fixes please see
    https://mariadb.com/docs/release-notes/community-server/10.6/10.6.24
    (LP: #2120204)
  * Update Lintian overrides for new files in latest upstream version
  * Add debian/source/local-options to suppress WolfSSL line ending errors

 -- Otto Kekäläinen <email address hidden> Fri, 10 Oct 2025 20:03:01 -0700

[Otto Kekäläinen (otto)]

Thanks!