Debian Patches
Status for mariadb/1:10.11.19-0+deb12u1
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| MDEV-37411-suppress-new-warning-about-native-aio.patch | Suppress native AIO warning introduced in 10.8.3 Upstream a87bb96 introduced a new warning, visible at least on all ppc64el and s390x builds which makes the post-build mariadb-test-test fail: [Warning] InnoDB: native AIO failed: falling back to innodb_use_native_aio=OFF The case of this is the ci environment only where there is insufficent fs.aio-max-nr configured. A such we are adding a suppression to the mtr only. The warning is valuable for users. Upstream MDEV-37411 has added a io_setup as a warning, which will fail in the CI environment, so we're pre-emptively suppressing this warning too. Unlike upstream MariaDB, in Debian we removed libaio in for Linux on MariaDB 10.6+ in 612630c6 and completely in 1d648d6f. This was re-added by upstream added a system variable innodb_linux_aio to control, and also provided automated fallback. As such we're readding it back too. With liburing still seccomp filterer in container environments having a libaio fallback is more valuable than the threads implementation of last resort. Edited & Updated: Daniel Black <daniel@mariabdb.org> |
Otto Kekäläinen <otto@debian.org> | yes | 2025-08-07 | ||
| CONC-821-Avoid-resetting-length-pointer-for-variable-leng.patch | CONC-821: Avoid resetting length pointer for variable-length types in mysql_stmt_bind_result Prior fix for CONC-821 initialized the length pointer (*bind->length) to 0 during mysql_stmt_bind_result() for variable-length types (strings, blobs, etc.). This broke third-party drivers and applications (e.g. Perl DBD::MariaDB, Qt, and others) that perform a re-bind step after fetching data but prior to reading/copying the bind buffer, as re-binding zeroed out the fetched length prematurely. Fix this regression by leaving the length pointer untouched during result binding for non-fixed-sized types. (cherry-picked from upstream libmariadb commit ead038d from MariaDB Connector C branch 3.4, can be dropped when importing the future 11.8.10) |
Georg Richter <georg@mariadb.com> | not-needed | https://github.com/mariadb-corporation/mariadb-connector-c/commit/ead038dc8a2b3d7819f87af33e14f105325f8cf9.patch | 2026-09-03 | |
| mroonga-mrn-lib-dirs-path-reproducible-build.patch | cmake: add support for reproducible buildS . We should use relative path not absolute path. We can use target without breaking reproducibility. |
Sutou Kouhei <kou@clear-code.com> | not-needed | upstream | https://github.com/mroonga/mroonga/issues/298#issuecomment-1030815927 | 2022-02-05 |
| env-perl-usr-bin-perl.patch | Fix perl path in scripts Fix Lintian issue https://lintian.debian.org/tags/incorrect-path-for-interpreter.html . Upstream will never accept this patch, see https://github.com/MariaDB/server/pull/1718 |
Otto Kekäläinen <otto@debian.org> | yes | https://patch-diff.githubusercontent.com/raw/MariaDB/server/pull/1718.patch | 2020-12-20 | |
| 0005-Use-Bash-as-interpreter-in-script-with-sh-incompatib.patch | Use Bash as interpreter in script with sh-incompatible syntax This script does not work with plain `sh`: $ sh -n mysql-test/lib/generate-ssl-certs.sh mysql-test/lib/generate-ssl-certs.sh: 78: Syntax error: "(" unexpected Hence a better interpreter choice is Bash. This issue was detected on Debian due to the Lintian nag: E: mariadb-test: shell-script-fails-syntax-check [usr/share/mariadb/mariadb-test/lib/generate-ssl-certs.sh] This script (and error) was introduced on commit c7313da, first released in 10.6.25. As that branch is no longer maintained, this fix targets oldest still maintained branch 10.11. |
Otto Kekäläinen <otto@kekalainen.net> | yes | 2026-10-12 |
All known versions for source package 'mariadb'
- 1:11.8.9+ds-4 (sid, forky)
- 1:11.8.8-0+deb13u1 (trixie-proposed-updates)
- 1:11.8.6-0+deb13u1 (trixie)
- 1:10.11.19-0+deb12u1 (bookworm-security)
- 1:10.11.18-0+deb12u1 (bookworm)