commit 1a0aef21c4a7eb5594231a3115a0c7055189a4b2
Author: Otto Kekäläinen <otto@debian.org>
Date: Wed Oct 8 11:53:42 2025 -0700
Salsa CI: Fix typos introduced in 855bc4f6
commit 5c75821ec17703b5d054cca55b42270f87591044
Author: Otto Kekäläinen <otto@debian.org>
Date: Wed Sep 17 14:43:42 2025 -0700
Salsa CI: Disable running `gbp setup-gitattributes`
If git-buildpackage applies the git attributes, the contents of the
checkout will be modified (e.g. Windows line endings converted to
Linux line endings) and xdelta3 will no longer be able to the delta
from pristine-tar to produce the original tarball.
Before:
$ if echo "$SALSA_CI_DISABLE_GBP_SETUP_GITATTRIBUTES" | grep -qvE '^(1|yes|true)$'; then test -r .gitattributes && gbp setup-gitattributes ; fi
$ if find . -maxdepth 3 -wholename "*/debian/source/format" -exec cat {} \; | grep -q '3.0 (gitarchive)'
...
gbp:info: All Orig tarballs 'mariadb_11.8.3.orig.tar.gz' found at '/builds/mariadb-team/mariadb-server/build/'
gbp:info: Creating /builds/mariadb-team/mariadb-server/build/mariadb_11.8.3.orig.tar.gz
gbp:error: Error creating mariadb_11.8.3.orig.tar.gz with attached signature file: Pristine-tar couldn't checkout "mariadb_11.8.3.orig.tar.gz": xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
pristine-tar: Failed to reproduce original tarball. Please file a bug report.
pristine-tar: failed to generate tarball
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
xdelta3: target window checksum mismatch: XD3_INVALID_INPUT
xdelta3: normally this indicates that the source file is incorrect
xdelta3: please verify the source file with sha1sum or equivalent
pristine-tar: Failed to reproduce original tarball. Please file a bug report.
pristine-tar: failed to generate tarball
Trying apt-get source mariadb=1:11.8.3-1 ...
Reading package lists...
NOTICE: 'mariadb' packaging is maintained in the 'Git' version control system at:
https://salsa.debian.org/mariadb-team/mariadb-server.git
Please use:
git clone https://salsa.debian.org/mariadb-team/mariadb-server.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 120 MB of source archives.
Get:1 http://deb.debian.org/debian sid/main mariadb 1:11.8.3-1 (tar) [120 MB]
Fetched 120 MB in 1s (101 MB/s)
Download complete and in download only mode
W: Download is performed unsandboxed as root as file 'mariadb_11.8.3.orig.tar.gz' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
'../mariadb_11.8.3.orig.tar.gz' -> '/builds/mariadb-team/mariadb-server/build/mariadb_11.8.3.orig.tar.gz'
gbp:info: Disabling 'cleaner' hook
gbp:info: Extracting 'mariadb_11.8.3.orig.tar.gz' to '/builds/mariadb-team/mariadb-server/build/mariadb-tmp'
gbp:info: Removing debian/ from unpacked upstream source at /builds/mariadb-team/mariadb-server/build/mariadb-tmp/debian
gbp:info: Exporting 'HEAD' to '/builds/mariadb-team/mariadb-server/build/mariadb-tmp'
gbp:info: Moving '/builds/mariadb-team/mariadb-server/build/mariadb-tmp' to '/builds/mariadb-team/mariadb-server/build/mariadb-11.8.3'
gbp:info: Performing the build
$ ls -lh ${BUILD_DIR}
total 115M
drwxrwxr-x 34 root root 4.0K Sep 26 18:15 mariadb-11.8.3
-rw-r--r-- 1 root root 115M Sep 26 18:32 mariadb_11.8.3.orig.tar.gz
After:
$ if echo "$SALSA_CI_DISABLE_GBP_SETUP_GITATTRIBUTES" | grep -qvE '^(1|yes|true)$'; then test -r .gitattributes && gbp setup-gitattributes ; fi
$ if find . -maxdepth 3 -wholename "*/debian/source/format" -exec cat {} \; | grep -q '3.0 (gitarchive)'
...
gbp:info: All Orig tarballs 'mariadb_11.8.3.orig.tar.gz' found at '/builds/mariadb-team/mariadb-server/build/'
gbp:info: Creating /builds/mariadb-team/mariadb-server/build/mariadb_11.8.3.orig.tar.gz
gbp:info: Disabling 'cleaner' hook
gbp:info: Exporting 'HEAD' to '/builds/mariadb-team/mariadb-server/build/mariadb-tmp'
gbp:info: Moving '/builds/mariadb-team/mariadb-server/build/mariadb-tmp' to '/builds/mariadb-team/mariadb-server/build/mariadb-11.8.3'
gbp:info: Performing the build
$ ls -lh ${BUILD_DIR}
total 115M
drwxrwxr-x 34 root root 4.0K Sep 26 22:07 mariadb-11.8.3
-rw-r--r-- 1 root root 115M Sep 26 22:24 mariadb_11.8.3.orig.tar.gz
-rw-r--r-- 1 root root 833 Sep 26 22:24 mariadb_11.8.3.orig.tar.gz.asc
commit fedc37a7e8a25806410601686321f1de8151bfb3
Author: Otto Kekäläinen <otto@debian.org>
Date: Fri Sep 26 11:14:08 2025 -0700
Add Lintian override for false error in test plugin
commit e21e05b12aec5434464f297c22d02a9b0a6e8682
Author: Otto Kekäläinen <otto@debian.org>
Date: Wed Sep 24 17:12:40 2025 -0700
Salsa CI: Remove custom CCACHE_MAXSIZE as Salsa CI now has 2GB by default
Also remove debug step about disk sizes as we already know what the
shares Salsa CI runners have 30 GB disks. If debug info like this is
needed about runners, it should be in Salsa CI itself.
commit 8aede151a1ce2c423456ddcbb5dc1cdb1880697f
Author: Otto Kekäläinen <otto@debian.org>
Date: Wed Sep 24 13:47:54 2025 -0700
Add debian/source/local-options to suppress WolfSSL line ending errors
This ensures `dpkg-source` will ignore any mismatches of what is in a
local git checkout versus what is in the upstream tarball, mainly the
Windows line endings that exists in the upstream tarball but which are
cleaned away but git automatically in Linux and which resulted in errors
such as:
dpkg-source: warning: file mariadb-11.8.3/extra/wolfssl/wolfssl/IDE/Espressif/ESP-IDF/examples/template/VisualGDB/wolfssl_template_IDF_v5.1_ESP32.vgdbproj has no final newline (either original or modified version)
dpkg-source: warning: file mariadb-11.8.3/extra/wolfssl/wolfssl/IDE/Espressif/ESP-IDF/examples/wolfssl_benchmark/VisualGDB/wolfssl_benchmark_IDF_v4.4_ESP32.vgdbproj has no final newline (either original or modified version)
dpkg-source: warning: file mariadb-11.8.3/extra/wolfssl/wolfssl/IDE/Espressif/ESP-IDF/examples/wolfssl_benchmark/VisualGDB/wolfssl_benchmark_IDF_v5_ESP32.vgdbproj has no final newline (either original or modified version)
dpkg-source: warning: file mariadb-11.8.3/extra/wolfssl/wolfssl/IDE/Espressif/ESP-IDF/examples/wolfssl_benchmark/VisualGDB/wolfssl_benchmark_IDF_v5_ESP32C3.vgdbproj has no final newline (either original or modified version)
dpkg-source: warning: file mariadb-11.8.3/extra/wolfssl/wolfssl/IDE/Espressif/ESP-IDF/examples/wolfssl_benchmark/VisualGDB/wolfssl_benchmark_IDF_v5_ESP32S3.vgdbproj has no final newline (either original or modified version)
commit 74231009808399787b6d06f5104f0f595f182ca5
Author: Otto Kekäläinen <otto@debian.org>
Date: Thu Sep 25 12:03:32 2025 -0700
Salsa CI: Stop testing updates from EOL Ubuntu 24.10
The Ubuntu Oracular archive has been shut down and can no longer be used
for testing upgrades from.
commit a5ea2666d87547105da545a69b23c9c175620dad
Author: Otto Kekäläinen <otto@debian.org>
Date: Tue Aug 26 12:35:13 2025 -0700
Salsa CI: Adapt to MySQL 8.0.43-3 no longer having a SysV init file
The commit https://salsa.debian.org/mariadb-team/mysql/-/commit/b75fb2e6b263459caebb8ab0353863bbed93aaca
most likely explains why these files are now gone from the mysql-server-8.0
package:
/etc/init.d/mysql
/etc/init/mysql.conf
/usr/share/doc/mysql-server-8.0/README.Debian.gz
/usr/share/doc/mysql-server-8.0/changelog.Debian.gz
/usr/share/doc/mysql-server-8.0/copyright
/usr/share/doc/mysql-server-8.0/examples/daemon_example.ini
/usr/share/doc/mysql-server-8.0/mysqld.sym.gz
/usr/share/lintian/overrides/mysql-server-8.0
/usr/share/mysql/debian_create_root_user.sql
/usr/share/mysql/docs/INFO_BIN
/usr/share/mysql/docs/INFO_SRC
/usr/share/mysql/echo_stderr
/usr/share/mysql/install_rewriter.sql
/usr/share/mysql/mysql-systemd-start
/usr/share/mysql/mysqld_multi.server
/usr/share/mysql/uninstall_rewriter.sql
/etc/apparmor.d/usr.sbin.mysqld
/etc/init.d/mysql
/etc/init/mysql.conf
/etc/logcheck/ignore.d.paranoid/mysql-server-8_0
/etc/logcheck/ignore.d.server/mysql-server-8_0
/etc/logcheck/ignore.d.workstation/mysql-server-8_0
/etc/logrotate.d/mysql-server
/etc/mysql/debian-start
/etc/mysql/mysql.cnf
/etc/mysql/mysql.conf.d/mysql.cnf
/etc/mysql/mysql.conf.d/mysqld.cnf
/lib/systemd/system/mysql.service
/usr/share/apport/package-hooks/source_mysql-8.0.py
/usr/share/doc/mysql-server-8.0/NEWS.Debian.gz
commit a712114437fac8e9b12d6621f37888a883dbe347
Author: Otto Kekäläinen <otto@debian.org>
Date: Tue Aug 26 12:31:34 2025 -0700
Salsa CI: Always in 'needs' also use 'artifacts'
If the 'build' job never ran or failed, the upgrade jobs might still try
to run regardless of the 'build' job status because of the 'when: always'
rule. Explicitly depend on the artifacts to prevent unnecessary runs when
the 'build' job status was something else than 'success'.
commit e4855c5b3d6e1aeb485f2ddc70a71e9d0650f2ef
Author: Otto Kekäläinen <otto@debian.org>
Date: Tue Aug 5 22:42:16 2025 -0700
Salsa CI: Manually link also /bin/rm to get past usrmerge upgrade
commit 8161c84da2700c30d8911118d670888fed5c95de
Author: Otto Kekäläinen <otto@debian.org>
Date: Tue Aug 5 19:22:52 2025 -0700
Salsa CI: Unify with similar job logic in Galera and Entr packages
commit 820bf7b53d89cbda4d40dc92f501c9f25a4a2603
Author: Otto Kekäläinen <otto@debian.org>
Date: Sat Aug 30 16:15:32 2025 -0700
Open new changelog entry
commit 9a29ad897c64de29af69970a69066746d7f1a31a
Author: Daniel Black <daniel@mariadb.org>
Date: Fri Aug 22 15:50:43 2025 +1000
MDEV-37411: re-enable AIO in Debian
Upstream in MDEV-36234, added the possibility of a
dual async-io stack, both libaio and liburing.
This can be controlled by the system variable
innodb_linux_aio, defaulting to auto. When run
in an environment where liburing isn't available
(container on old kernels, containers seccomp rules,
disable at the kernel leve, insufficent locked
resources, etc), its recommend by upstream and
advisable to fall back to libaio.
As such we'll need to link again to libaio by
adding libaio to the build dependences and using
an explicit WITH_AIO=ON as a cmake build flag.
In appreciation that launchpad, and potentially
salsa aren't sufficiently configured for parallel
mtr runs with libaio, or liburing, we surpress
those warnings in MTR.
Among the 9 debian patches available in version 1:11.8.3-1 of the package, we noticed the following issues:
![[bug history graph]](https://qa.debian.org/data/bts/graphs/m/mariadb.png){kind=link}