Comment 11 for bug 1949565

Hi,
this is a really sad case, but as Ubuntu I'm not seeing what else we could do here than leaving things as is. The delivery of security fixes is important to the majority of users.

In this particular case in the referenced upstream bug and further links from there [2] indicate that Microsoft <-> Mysql have given up to implement something on the Azure DB side to work with the security-fixed version of mysql. But on the other hand we can not really revert that change to provide mysql re-opening known security issues.

It seems in [2] that Microsoft has settled on "then use Flexible Server instead of Single Server". I have to admit I do not know what all that implied (more cost, data migration, ... it does not seem to be as drop-in replacement to me :-/) but right now as sad as it is this seems to be the only way out of this for affected users.

I see that @emgag continues to use the older builds, while that works it means you lack CVE fixes and with every new upload there will be more that you miss. So please consider using that only as fallback until you have made a transition to the "Flexible Server" or other alternatives.

If there is a way to retain the CVE fix, but a follow up change allows to use the "Azure DB for Mysql - Single server" again please speak up and let us know. But unless such a thing exists this has to be "incomplete" as no one can really act on it for an Ubuntu upload to fix it.

[1]: https://bugs.mysql.com/bug.php?id=105288
[2]: https://docs.microsoft.com/en-us/azure/mysql/concepts-compatibility#mysql-drivers