MariaDB
WIP: Misc Debian related fixes + MDEV-28640
WIP
A commit that fixes MDEV-28640 is still missing from this PR, pending for it to be finalized.
Description
See commit messages for details. All changes are related to Debian packaging, so grouped them in one PR.
How can this PR be tested?
Debian packaging is extensively tested by Salsa-CI. I will post a link to the Salsa-CI run once #2299 is fixed so that there is actually a working Salsa-CI on branch 10.6 to compare this PR to.
Basing the PR against the correct MariaDB version
- [x] This is a bug fix and the PR is based against the earliest branch in which the bug can be reproduced
Backward compatibility
These changes are fully backwards compatible. The changes will be visible to end users who install/upgrade MariaDB on Debian. The nature of changes is bugfixes and is the fixes are correct, there will be no negative effect on users.
I'll test this on salsa is it fixing last 10.6 compiling problem.. Imported to branch: ottok-10.6-salsa-ci-oct2022-MDEV-28834+28640 which now contains all changes to make 10.6 work if they are merged. Just to see if they are doing things ok.
Is there something missing as this seems to be good? As it's currently WIP?
This is still in the works, do not close. Updates in https://jira.mariadb.org/browse/MDEV-28640 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035949
In Debian we ended up introducing mariadb-server-10.5 as an empty metapackage, might need to do that upstream as well.
This has been fixed in Debian since June 2023, but never updated here as it is unclear how to test upgrades with upstream buildbot, and the debian/salsa-ci.yml in upstream branch hasn't been working for a long time as upstream development isn't using it at all to test for any Debian regressions.
Considering https://jira.mariadb.org/browse/MDEV-28640 hasn't had any comments since late 2023, I assume it was fixed upstream in some other way, or that the whole 10.5 and 10.6 upgrade to newer isn't a thing anymore.