Dear maintainer(s),

With a recent upload of mariadb the autopkgtest of mariadb-10.6 fails in
testing on amd64 and arm64 when that autopkgtest is run with the binary
packages of mariadb from unstable. It passes when run with only packages
from testing. In tabular form:

                        pass            fail
mariadb                from testing    1:10.11.1-2
mariadb-10.6           from testing    1:10.6.11-2
versioned deps [0]     from testing    from unstable
all others             from testing    from testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of mariadb to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
mariadb/1:10.11.1-2. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=mariadb

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mariadb-10.6/31062126/log.gz

+ which systemctl
+ echo Found systemctl, continuing smoke test..
+ mysql
Running test 'smoke'
/usr/bin/systemctl
Found systemctl, continuing smoke test..
+ mysql testdatabase
+ + mysql --batch --skip-column-names --user=testuser
--password=testpassword testdatabase
echo SELECT bar+1 FROM foo;
+ result=42
+ [ 42 != 42 ]
+ mysql --user=testuser --password=testpassword testdatabase
+ mysql
+ mariadb
ERROR 1231 (42000) at line 1: Variable 'innodb_compression_algorithm'
can't be set to the value of 'lz4'
autopkgtest [04:36:43]: test smoke

Hi!

The error message "Variable 'innodb_compression_algorithm' can't be
set to the value of 'lz4'" is from the first test, and it fails.
Actually all tests fail because in MariaDB 10.11 the compression
methods are packaged in separate packages.

The root cause here is that the test in 10.6 depends on simply
'mariadb-server'. With a new 'mariadb-server' from 10.11 the test of
10.6 will fail. The test would not fail if the autopkgtests originally
had a dependency on 'mariadb-server-10.6'.

It does not seem worth the effort to upload a new src:mariadb-10.6
just to fix this. It is a pure test issue and not a symptom of a real
failure.

Can we have a temporary override to shut down the src:mariadb-10.6
autopkgtests in Debian CI so that 10.11 can enter Debian
testing/Bookworm and I can then file request to remove
src:mariadb-10.6 from testing and unstable?

forwarded MDEV-30611 https://jira.mariadb.org/browse/MDEV-30611
thanks

Hello,

Bug #1030604 in mariadb reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/5545bb341808cef8a4227b55b0c75e331cc48c96
This will ensure 100% backwards compatibility with previous versions
of MariaDB in Debian, and also the old src:mariadb-10.6 autopkgtests pass.

- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030604
- https://ci.debian.net/packages/m/mariadb-10.6/

This commit can later be reverted if needed and compression method plugins
demoted back to Recommends.
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030604

We believe that the bug you reported is fixed in the latest version of
mariadb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1030604@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otto Kekäläinen <otto@debian.org> (supplier of updated mariadb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 09 Feb 2023 08:40:34 -0800
Source: mariadb
Binary: libmariadb-dev libmariadb-dev-compat libmariadb3 libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core mariadb-client mariadb-server-core mariadb-server mariadb-backup mariadb-plugin-connect mariadb-plugin-s3 mariadb-plugin-rocksdb mariadb-plugin-oqgraph mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-cracklib-password-check mariadb-plugin-hashicorp-key-management mariadb-plugin-provider-bzip2 mariadb-plugin-provider-lz4 mariadb-plugin-provider-lzma mariadb-plugin-provider-lzo mariadb-plugin-provider-snappy mariadb-test mariadb-test-data
Architecture: source
Version: 1:10.11.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>
Changed-By: Otto Kekäläinen <otto@debian.org>
Description:
 libmariadb-dev - MariaDB database development files
 libmariadb-dev-compat - MariaDB Connector/C, compatibility symlinks
 libmariadb3 - MariaDB database client library
 libmariadbd-dev - MariaDB embedded database, development files
 libmariadbd19 - MariaDB embedded database, shared library
 mariadb-backup - Backup tool for MariaDB server
 mariadb-client - MariaDB database client binaries
 mariadb-client-core - MariaDB database core client binaries
 mariadb-common - MariaDB common configuration files
 mariadb-plugin-connect - Connect storage engine for MariaDB
 mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB
 mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client
 mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server
 mariadb-plugin-hashicorp-key-management - Hashicorp Key Management plugin for MariaDB
 mariadb-plugin-mroonga - Mroonga storage engine for MariaDB
 mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB
 mariadb-plugin-provider-bzip2 - BZip2 compression support in the server and storage engines
 mariadb-plugin-provider-lz4 - LZ4 compression support in the server and storage engines
 mariadb-plugin-provider-lzma - LZMA compression support in the server and storage engines
 mariadb-plugin-provider-lzo - LZO compression support in the server and storage engines
 mariadb-plugin-provider-snappy - Snappy compression support in the server and storage engines
 mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB
 mariadb-plugin-s3 - Amazon S3 archival storage engine for MariaDB
 mariadb-plugin-spider - Spider storage engine for MariaDB
 mariadb-server - MariaDB database server binaries
 mariadb-server-core - MariaDB database core server files
 mariadb-test - MariaDB database regression test suite
 mariadb-test-data - MariaDB database regression test suite - data files
Closes: 1006529 1030604
Changes:
 mariadb (1:10.11.1-4) unstable; urgency=medium
 .
   [ Otto Kekäläinen ]
   * Have all compression plugins as Depends for mariadb-server (Closes: #1030604)
   * Update existing patch with latest upstream PR#2448 version 0284207
   * Temporarily disable MTR on s390x as Debian buildd seems unstable
     (Related: #1030510)
   * Add upstream patch to fix build failure on HPPA (Closes: #1006529)
   * Refresh patches and include references to Debian bugs they should fix
 .
   [ Gianfranco Costamagna ]
   * Drop riscv64 rules latomic hack, use upstream PR#2477 instead
     (Related: #1024041)
Checksums-Sha1:
 0a54aff920cae43149cf7f10af042e0ba04520ee 5004 mariadb_10.11.1-4.dsc
 9187c61ae0a86bc9937e9f5d45bbe7461316aefe 267892 mariadb_10.11.1-4.debian.tar.xz
 10b1965c2887e26ad3633c1f45312735326eefe1 9517 mariadb_10.11.1-4_source.buildinfo
Checksums-Sha256:
 551a32a264185e772fb4a87a67dd814489d2e7b54cb8ba344903fe865365c6f6 5004 mariadb_10.11.1-4.dsc
 caf9614de002a8ecb87dcb7e1a0d91731bf36bf706315c923b32cdab16bdcad8 267892 mariadb_10.11.1-4.debian.tar.xz
 2df25e62b5365483cd74bde03bab3504e85558fb32b086c60dfa2498f26f11f8 9517 mariadb_10.11.1-4_source.buildinfo
Files:
 9e1eb731f39bf0949d9a3edb2082270f 5004 database optional mariadb_10.11.1-4.dsc
 554700e4baf1fab5c4827c87eac28421 267892 database optional mariadb_10.11.1-4.debian.tar.xz
 bbd32d04fdb678f89f82deb2a64703bd 9517 database optional mariadb_10.11.1-4_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAmPlVB4ACgkQvthEn87o
2ogvhQ//da+2dx8E7WPzk9mEU0a7sZnXVM5ynPIt8zU1DNLT6HsyylXQVPE7Q65j
aOjLNdJEkZeRXjVgpt+qW49M2+Y32Kdi+Reop+W/3izqgLThkzZQ/sOPWA+ys0lD
U4RfSmfESay3RCPg1hOOnxf/+4LVM0JsGSY6DKjquNu/TkCWlzu1hkdlrIYXIEkP
fAZrZds2SePo+CxXHO53k6nkUT00k5U+EfU3xQyEhxGiPSfps/WYTOdpfQeqCR6m
D00RP3jtdZjLBxCzTXENOgRjMj/ejS//YyHx5IFnqTQAKFk8P6XaGTMpoaB0rrHr
+jxyrsiNE9Hjbi4zsfZKJnIr9NLbbGSPPDaMtWZcxNtF4vOmdr0OGZT/xpgC3axh
w0L7+kMS7k0P/NYRFqExwA1tbin9QR+P5zkDg7oYziv5Z4Ktf7LzcsrrzUO/+i0F
QbZcio0+9TLRQLjEvSEB5qgC0VisipPi6BmP7m/CEpNVx0rEDwDoGaUcNBZafwBc
+7s7j8fLJ6FO5rss0MSQIl+ZKm23Th1J9A6I29jbb4o4kTpgCDB/v+HTLHDLNCh8
jRniXtYgHQ1Ya3wRoya2wSF/fYWLOBUNgq5PdbtPCfDRa9hitlAp6onti+gVMSHb
IL/nM15O4klraU32Avo2KAsv0aKzq3S0YPt01jCGApmU+CpBsxE=
=PC2C
-----END PGP SIGNATURE-----

Since https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/36
was merged it fixed Bug#1031116 (apt ordering broke Cacti
autopkgtests) but now this came back - the mariadb-10.6 autopkgtests
cannot pass as they will install mariadb-server version 1:10.11.2-1
which only works with the autopkgtests from 10.11 and the old
autopkgtests in 10.6 will never pass running old tests with new
binaries.

This should just be ignored and eventually fixed by removing
mariadb-10.6 from testing and unstable.

This failure should just be ignored

Executing the src:mariadb-10.6 removal request filed in Bug#1033485
would fix Bug#1030604 about mariadb-10.6 autopkgtests failing in
Debian unstable.

(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030604)

Is it 10.5 or 10.6 that should be removed?  Subject says one and the body says the other.

Scott K

As MariaDB 10.6 and 10.11 are now removed and replaced by MariaDB
(11.8), this bug can be closed.