[debian-mysql] MariaDB upgrades for Debian/Ubuntu pending: request for review and contribtions

[Otto Kekäläinen]

Hi!

> I've asked the Launchpad devs for input and I intend to follow up from
> that side (if I don't, please chase me). But, looking at this from
> multiple angles:

I have followed up in IRC and seems Coling commented the issue today:
https://bugs.launchpad.net/launchpad-buildd/+bug/1943292

> On Sun, Nov 21, 2021 at 06:42:31PM -0800, Otto Kekäläinen wrote:
> > Unfortunately it is not just one test, it is the whole mariadbd that fails
> > to start due to lacking I/O facilities.
>
> Is it guaranteed that _all_ Debian users will be running a kernel with
> io_uring support, or that this is an acceptable minimum baseline to
> assume in Debian (bookworm)? Even if true, what if a user runs a custom
> kernel without that support? Is it acceptable for mariadbd to fail to
> start in this case? Does MariaDB retain support for building and running
> without io_uring support at all?

It is only a problem if the kernel is too old. All Bookworm users are
guaranteed to have a new enough kernel.

On Launchpad the armhf builds pass, as that arch does not support
uring and does not get uring built into it - thus there is no kernel
incompatibility when it runs on Launchpad.

> I'm not aware of any specific compatibility rules in Debian or Ubuntu
> regarding this. But regardless of support on Ubuntu's builders, it would
> be certainly more robust all round, including for user experience, if
> MariaDB could handle this situation better by dealing with it at
> runtime. Maybe you could make that request upstream, please?

There is an upstream issue where Marko explains more about what is
going on: https://jira.mariadb.org/browse/MDEV-26569

I don't think this issue is grave. Let's just wait for Launchpad
kernels to catch up and then it should work.

- Otto