I noticed the MariaDB 1:11.8.6-2 that entered Ubuntu resolute-proposed
on Feb 19th did so apparently a few hours after teh Debian import freeze
started. Hence I plan to file a "FFE: Sync mariadb 1:11.8.6-2 (universe)
from Debian unstable (main)" for the Release Team to approve and sync,
unless of course someone else triggers a sync some other path before
that.
mariadb (1:11.8.6-2) unstable; urgency=medium
.
[ Aquila Macedo ]
* Add systemd hardening patch for MariaDB units (Closes: #1123021)
.
[ Otto Kekäläinen ]
* Add Lintian override for potentially false new error about embedded
libminizip
* Remove patch for x32 compilation now supposedly fixed upstream in ff4209f
* Update patch statuses and Forwarded fields to match latest
* Fix path to mariadb-server.README in mariadb-secure-install
(Closes: #1127863)
* Add preliminary upstream patch to fix MDEV-38811 that affected Akonadi and
any other use case that relies on 'skip-grant-tables' (Closes: #1127431)
* Add functional AppArmor profile for MariaDB 11.8 but keep it in 'complain'
mode for now to collect real usage experience, and enabling 'enforce' mode
some day in the future when likelihood of unanticipated AppArmor denials
is close to zero (Closes: #875890)
I plan to also upload and request a FFE for a final -3 version, which will have
the AppArmor profile in enforce mode, some time before the Beta Freeze, which
according to
https://discourse.ubuntu.com/t/resolute-raccoon-release-schedule/47198 is on
March 24th. I can do it earlier than that too if there are more users reporting
that they haven't had issues with the new AppArmor profile.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122095
Title:
[MIR] mariadb
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2122095/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
