mysql-test/lib/process-purecov-annotations.pl | 2 1 + 1 - 0 !
mysql-test/lib/v1/mysql-test-run.pl | 2 1 + 1 - 0 !
mysql-test/mariadb-stress-test.pl | 2 1 + 1 - 0 !
mysql-test/mariadb-test-run.pl | 2 1 + 1 - 0 !
mysql-test/std_data/checkDBI_DBD-MariaDB.pl | 2 1 + 1 - 0 !
mysql-test/suite/engines/rr_trx/run_stress_tx_rr.pl | 2 1 + 1 - 0 !
mysql-test/suite/funcs_1/lib/DataGen_local.pl | 2 1 + 1 - 0 !
mysql-test/suite/funcs_1/lib/DataGen_modify.pl | 2 1 + 1 - 0 !
mysql-test/suite/funcs_2/lib/gen_charset_utf8.pl | 2 1 + 1 - 0 !
mysql-test/suite/rpl/extension/checksum.pl | 2 1 + 1 - 0 !
scripts/mytop.sh | 2 1 + 1 - 0 !
11 files changed, 11 insertions(+), 11 deletions(-)

 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

storage/mroonga/CMakeLists.txt | 12 4 + 8 - 0 !
1 file changed, 4 insertions(+), 8 deletions(-)

 [patch] cmake: add support for reproducible builds
 .
 We should use relative path not absolute path.
 We can use target without breaking reproducibility.

storage/innobase/os/os0file.cc | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 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

Unlike upstream MariaDB, in Debian we removed libaio in for Linux on
MariaDB 10.6+ in 612630c6 and completely in 1d648d6f. Thus the build
will not have libaio at all on any platform in Debian, and the warning
is useless.

This might not be the optimal solution, but at least suppressing the warning
will unblock the 11.8.3 release for now.