Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

https://people.debian.org/~sanvila/build-logs/202606/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:libdbd-mariadb-perl, so that this is still
visible in the BTS web page for this package.

Thanks.
--------------------------------------------------------------------------------
[...]
 debian/rules clean
dh clean
   dh_clean
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<<PKGBUILDDIR>>'
LC_ALL=C.UTF-8 dh_auto_configure
	/usr/bin/perl Makefile.PL INSTALLDIRS=vendor OPTIMIZE="-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" LD="x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wl,-z,relro -Wl,-z,now"
I will use the following settings for compiling and testing:

  cflags       (mysql_config) = -I/usr/include/mariadb -I/usr/include/mariadb/mysql
  libs         (mysql_config) = -L/usr/lib/x86_64-linux-gnu/ -lmariadb

[... snipped ...]

ok 219 - $sth->bind_param(1, 1, DBI::SQL_INTEGER) processes get magic on param only once
ok 220 - $sth->bind_param(1, 1, DBI::SQL_INTEGER) does not process set magic on param
ok 221 - $dbh->prepare(SELECT * FROM t WHERE i = '1' OR i = ?) processes get magic on statement only once
ok 222 - $dbh->prepare(SELECT * FROM t WHERE i = '1' OR i = ?) does not process set magic on statement
ok 223 - $sth->bind_param(1, 1, DBI::SQL_FLOAT) processes get magic on param only once
ok 224 - $sth->bind_param(1, 1, DBI::SQL_FLOAT) does not process set magic on param
ok 225 - $dbh->do(SELECT * FROM t WHERE i = '1.1' OR i = ?, {}, 1.1) processes get magic on statement only once
ok 226 - $dbh->do(SELECT * FROM t WHERE i = '1.1' OR i = ?, {}, 1.1) does not process set magic on statement
ok 227 - $dbh->do(SELECT * FROM t WHERE i = '1.1' OR i = ?, {}, 1.1) processes get magic on param only once
ok 228 - $dbh->do(SELECT * FROM t WHERE i = '1.1' OR i = ?, {}, 1.1) does not process set magic on param
ok 229 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = '1.1' OR i = ?, {}, 1.1) processes get magic on statement only once
ok 230 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = '1.1' OR i = ?, {}, 1.1) does not process set magic on statement
ok 231 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = '1.1' OR i = ?, {}, 1.1) processes get magic on param only once
ok 232 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = '1.1' OR i = ?, {}, 1.1) does not process set magic on param
ok 233 - $dbh->prepare(SELECT * FROM t WHERE i = '1.1' OR i = ?) processes get magic on statement only once
ok 234 - $dbh->prepare(SELECT * FROM t WHERE i = '1.1' OR i = ?) does not process set magic on statement
ok 235 - $sth->execute(1.1) processes get magic on param only once
ok 236 - $sth->execute(1.1) does not process set magic on param
ok 237 - $dbh->prepare(SELECT * FROM t WHERE i = '1.1' OR i = ?) processes get magic on statement only once
ok 238 - $dbh->prepare(SELECT * FROM t WHERE i = '1.1' OR i = ?) does not process set magic on statement
ok 239 - $sth->bind_param(1, 1.1) processes get magic on param only once
ok 240 - $sth->bind_param(1, 1.1) does not process set magic on param
ok 241 - $dbh->prepare(SELECT * FROM t WHERE i = '1.1' OR i = ?) processes get magic on statement only once
ok 242 - $dbh->prepare(SELECT * FROM t WHERE i = '1.1' OR i = ?) does not process set magic on statement
ok 243 - $sth->bind_param(1, 1.1, DBI::SQL_INTEGER) processes get magic on param only once
ok 244 - $sth->bind_param(1, 1.1, DBI::SQL_INTEGER) does not process set magic on param
ok 245 - $dbh->prepare(SELECT * FROM t WHERE i = '1.1' OR i = ?) processes get magic on statement only once
ok 246 - $dbh->prepare(SELECT * FROM t WHERE i = '1.1' OR i = ?) does not process set magic on statement
ok 247 - $sth->bind_param(1, 1.1, DBI::SQL_FLOAT) processes get magic on param only once
ok 248 - $sth->bind_param(1, 1.1, DBI::SQL_FLOAT) does not process set magic on param
ok 249 - $dbh->do(SELECT * FROM t WHERE i = NULL OR i = ?, {}, undef) processes get magic on statement only once
ok 250 - $dbh->do(SELECT * FROM t WHERE i = NULL OR i = ?, {}, undef) does not process set magic on statement
ok 251 - $dbh->do(SELECT * FROM t WHERE i = NULL OR i = ?, {}, undef) processes get magic on param only once
ok 252 - $dbh->do(SELECT * FROM t WHERE i = NULL OR i = ?, {}, undef) does not process set magic on param
ok 253 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = NULL OR i = ?, {}, undef) processes get magic on statement only once
ok 254 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = NULL OR i = ?, {}, undef) does not process set magic on statement
ok 255 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = NULL OR i = ?, {}, undef) processes get magic on param only once
ok 256 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = NULL OR i = ?, {}, undef) does not process set magic on param
ok 257 - $dbh->prepare(SELECT * FROM t WHERE i = NULL OR i = ?) processes get magic on statement only once
ok 258 - $dbh->prepare(SELECT * FROM t WHERE i = NULL OR i = ?) does not process set magic on statement
ok 259 - $sth->execute(undef) processes get magic on param only once
ok 260 - $sth->execute(undef) does not process set magic on param
ok 261 - $dbh->prepare(SELECT * FROM t WHERE i = NULL OR i = ?) processes get magic on statement only once
ok 262 - $dbh->prepare(SELECT * FROM t WHERE i = NULL OR i = ?) does not process set magic on statement
ok 263 - $sth->bind_param(1, undef) processes get magic on param only once
ok 264 - $sth->bind_param(1, undef) does not process set magic on param
ok 265 - $dbh->prepare(SELECT * FROM t WHERE i = NULL OR i = ?) processes get magic on statement only once
ok 266 - $dbh->prepare(SELECT * FROM t WHERE i = NULL OR i = ?) does not process set magic on statement
ok 267 - $sth->bind_param(1, undef, DBI::SQL_INTEGER) processes get magic on param only once
ok 268 - $sth->bind_param(1, undef, DBI::SQL_INTEGER) does not process set magic on param
ok 269 - $dbh->prepare(SELECT * FROM t WHERE i = NULL OR i = ?) processes get magic on statement only once
ok 270 - $dbh->prepare(SELECT * FROM t WHERE i = NULL OR i = ?) does not process set magic on statement
ok 271 - $sth->bind_param(1, undef, DBI::SQL_FLOAT) processes get magic on param only once
ok 272 - $sth->bind_param(1, undef, DBI::SQL_FLOAT) does not process set magic on param
ok 273 - $dbh->do(SELECT * FROM t WHERE i = 'XX' OR i = ?, {}, XX) processes get magic on statement only once
ok 274 - $dbh->do(SELECT * FROM t WHERE i = 'XX' OR i = ?, {}, XX) does not process set magic on statement
ok 275 - $dbh->do(SELECT * FROM t WHERE i = 'XX' OR i = ?, {}, XX) processes get magic on param only once
ok 276 - $dbh->do(SELECT * FROM t WHERE i = 'XX' OR i = ?, {}, XX) does not process set magic on param
ok 277 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = 'XX' OR i = ?, {}, XX) processes get magic on statement only once
ok 278 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = 'XX' OR i = ?, {}, XX) does not process set magic on statement
ok 279 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = 'XX' OR i = ?, {}, XX) processes get magic on param only once
ok 280 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = 'XX' OR i = ?, {}, XX) does not process set magic on param
ok 281 - $dbh->prepare(SELECT * FROM t WHERE i = 'XX' OR i = ?) processes get magic on statement only once
ok 282 - $dbh->prepare(SELECT * FROM t WHERE i = 'XX' OR i = ?) does not process set magic on statement
ok 283 - $sth->execute(XX) processes get magic on param only once
ok 284 - $sth->execute(XX) does not process set magic on param
ok 285 - $dbh->prepare(SELECT * FROM t WHERE i = 'XX' OR i = ?) processes get magic on statement only once
ok 286 - $dbh->prepare(SELECT * FROM t WHERE i = 'XX' OR i = ?) does not process set magic on statement
ok 287 - $sth->bind_param(1, XX) processes get magic on param only once
ok 288 - $sth->bind_param(1, XX) does not process set magic on param
ok 289 - $dbh->do(SELECT * FROM t WHERE i = 'Ā' OR i = ?, {}, Ā) processes get magic on statement only once
ok 290 - $dbh->do(SELECT * FROM t WHERE i = 'Ā' OR i = ?, {}, Ā) does not process set magic on statement
ok 291 - $dbh->do(SELECT * FROM t WHERE i = 'Ā' OR i = ?, {}, Ā) processes get magic on param only once
ok 292 - $dbh->do(SELECT * FROM t WHERE i = 'Ā' OR i = ?, {}, Ā) does not process set magic on param
ok 293 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = 'Ā' OR i = ?, {}, Ā) processes get magic on statement only once
ok 294 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = 'Ā' OR i = ?, {}, Ā) does not process set magic on statement
ok 295 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = 'Ā' OR i = ?, {}, Ā) processes get magic on param only once
ok 296 - $dbh->selectall_arrayref(SELECT * FROM t WHERE i = 'Ā' OR i = ?, {}, Ā) does not process set magic on param
ok 297 - $dbh->prepare(SELECT * FROM t WHERE i = 'Ā' OR i = ?) processes get magic on statement only once
ok 298 - $dbh->prepare(SELECT * FROM t WHERE i = 'Ā' OR i = ?) does not process set magic on statement
ok 299 - $sth->execute(Ā) processes get magic on param only once
ok 300 - $sth->execute(Ā) does not process set magic on param
ok 301 - $dbh->prepare(SELECT * FROM t WHERE i = 'Ā' OR i = ?) processes get magic on statement only once
ok 302 - $dbh->prepare(SELECT * FROM t WHERE i = 'Ā' OR i = ?) does not process set magic on statement
ok 303 - $sth->bind_param(1, Ā) processes get magic on param only once
ok 304 - $sth->bind_param(1, Ā) does not process set magic on param
ok
t/manifest.t ............................ skipped: these tests are for release testing
t/pod.t ................................. skipped: Test::Pod 1.41 required for testing POD
t/rt110983-valid-mysqlfd.t ..............
1..4
ok 1 - $dbh->mariadb_sockfd returns valid file descriptor when $dbh connection is open
ok 2 - $dbh->{mariadb_sockfd} returns valid file descriptor when $dbh connection is open
ok 3 - $dbh->mariadb_sockfd returns undef when $dbh connection was closed
ok 4 - $dbh->{mariadb_sockfd} returns undef when $dbh connection was closed
ok

#   Failed test at t/rt118977-zerofill.t line 21.
#          got: ''
#     expected: '1234567890'
# Looks like you failed 1 test of 12.
t/rt118977-zerofill.t ...................
1..12
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
not ok 11
ok 12
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/12 subtests
t/rt122541-decimals.t ...................
1..2
ok 1 - floats with fixed-length of decimals returns correct value for mariadb_server_prepare=0
ok 2 - floats with fixed-length of decimals returns correct value for mariadb_server_prepare=1
ok
t/rt25389-bin-case.t ....................
1..8
ok 1 - select name from `dbd-mysql-latin1-`
ok 2 - select name from `dbd-mysql-latin1-` where name = 'AA' OR name = 'Aa' OR name = 'aa' OR name = 'aA'
ok 3 - select name from `dbd-mysql-latin1-unique`
ok 4 - select name from `dbd-mysql-latin1-unique` where name = 'AA' OR name = 'Aa' OR name = 'aa' OR name = 'aA'
ok 5 - select name from `dbd-mysql-utf8-`
ok 6 - select name from `dbd-mysql-utf8-` where name = 'AA' OR name = 'Aa' OR name = 'aa' OR name = 'aA'
ok 7 - select name from `dbd-mysql-utf8-unique`
ok 8 - select name from `dbd-mysql-utf8-unique` where name = 'AA' OR name = 'Aa' OR name = 'aa' OR name = 'aA'
ok
t/rt50304-column_info_parentheses.t .....
ok 1
ok 2 - create table dbd_mysql_rt50304_column_info
ok 3 - problem_column values
ok 4 - problem_column first value
ok 5 - problem_column second value
ok 6 - regular_column values
ok 7 - regular_column first value
ok 8 - regular_column second value
ok 9
ok 10
1..10
ok
t/rt61849-bind-param-buffer-overflow.t ..
1..3
ok 1
ok 2 - bind_param failed on incorrect numeric value
ok 3 - perl interpreter did not crash
ok
t/rt83494-quotes-comments.t .............
ok 1 - created statement hande
ok 2 - executing
ok 3 - values
ok 4 - finish
ok 5 - created statement hande
ok 6 - executing
ok 7 - values
ok 8 - finish
ok 9 - created statement hande
ok 10 - executing
ok 11 - values
ok 12 - finish
ok 13 - created statement hande
ok 14 - executing
ok 15 - values
ok 16 - finish
ok 17 - disconnecting from dbh
1..17
ok
t/rt86153-reconnect-fail-memory.t ....... skipped: $ENV{EXTENDED_TESTING} is not set
t/rt88006-bit-prepare.t .................
ok 1 - create table for prepare
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9 - fetchrow_hashref for prepare
ok 10 - id test contents
ok 11 - flags has contents
ok 12
ok 13
ok 14 - fetchrow_hashref for prepare with more then 32 bits
ok 15 - id test contents
ok 16 - flags has contents
ok 17
ok 18
ok 19 - fetchrow_hashref for prepare with binary insert
ok 20 - id test contents
ok 21 - flags has contents
ok 22
ok 23
ok 24 - fetchrow_hashref for prepare with BIN()
ok 25 - id test contents
ok 26 - flags has contents
ok 27
ok 28
ok 29 - fetchrow_hashref for prepare with BIN() and more then 32 bits
ok 30 - id test contents
ok 31 - flags has contents
ok 32
ok 33
ok 34 - fetchrow_hashref for prepare with BIN() and with binary insert
ok 35 - id test contents
ok 36 - flags has contents
ok 37
ok 38 - create table for noprepare
ok 39
ok 40
ok 41
ok 42
ok 43
ok 44
ok 45
ok 46 - fetchrow_hashref for noprepare
ok 47 - id test contents
ok 48 - flags has contents
ok 49
ok 50
ok 51 - fetchrow_hashref for noprepare with more then 32 bits
ok 52 - id test contents
ok 53 - flags has contents
ok 54
ok 55
ok 56 - fetchrow_hashref for noprepare with binary insert
ok 57 - id test contents
ok 58 - flags has contents
ok 59
ok 60
ok 61 - fetchrow_hashref for noprepare with BIN()
ok 62 - id test contents
ok 63 - flags has contents
ok 64
ok 65
ok 66 - fetchrow_hashref for noprepare with BIN() and more then 32 bits
ok 67 - id test contents
ok 68 - flags has contents
ok 69
ok 70
ok 71 - fetchrow_hashref for noprepare with BIN() and with binary insert
ok 72 - id test contents
ok 73 - flags has contents
ok 74
1..74
ok
t/rt91715.t .............................
1..6
ok 1
ok 2
ok 3 - mariadb_use_result set to 0
ok 4
ok 5
ok 6 - mariadb_use_result set to 1
ok

Test Summary Report
-------------------
t/50chopblanks.t                      (Wstat: 2048 (exited 8) Tests: 180 Failed: 8)
  Failed tests:  140-147
  Non-zero exit status: 8
t/rt118977-zerofill.t                 (Wstat: 256 (exited 1) Tests: 12 Failed: 1)
  Failed test:  11
  Non-zero exit status: 1
Files=90, Tests=3582, 32 wallclock secs ( 0.21 usr  0.10 sys +  3.87 cusr  1.09 csys =  5.27 CPU)
Result: FAIL
Failed 2/90 test programs. 9/3582 subtests failed.
make[2]: *** [Makefile:1258: test_dynamic] Error 255
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_test: error: make -j2 test TEST_VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:32: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:23: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit status 2
--------------------------------------------------------------------------------

Santiago is very fast at reporting FTBFS regressions, and the filing
fits with being caused by the upload of 1:11.8.8-1 to unstable.

I can reproduce in trixie that libdbd-mariadb-perl builds with
1:11.8.6-0+deb13u1 from stable but does FTBFS with 1:11.8.8-0+deb13u1
from pu.

In both unstable and stable the autopkgtest shows the same failures
and blames mariadb 11.8.8 (but only neutral due to flaky):
https://ci.debian.net/packages/libd/libdbd-mariadb-perl/testing/amd64/
https://ci.debian.net/packages/libd/libdbd-mariadb-perl/stable/amd64/

While building locally there was always a stray mysqld process left
after the build (only with 11.8.8), this is also seen in reproducible:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libdbd-mariadb-perl.html
  W: Stray processes left from build:
  ...
     CGroup: /system.slice/system-pbuilder.slice/system-pbuilder-build.slice/system-pbuilder-build-libdbd\x2dmariadb\x2dperl_1.22\x2d1.slice/system-pbuilder-build-libdbd\x2dmariadb\x2dperl_1.22\x2d1-2487514.slice
             `-run-p2505164-i40247590.scope
               `-2509485 /usr/sbin/mysqld --no-defaults --user=pbuilder1 --socket=/build/reproducible-path/libdbd-mariadb-perl-1.22/t/testdb/mysql.sock --datadir=/build/reproducible-path/libdbd-mariadb-perl-1.22/t/testdb --pid-file=/build/reproducible-path/libdbd-mariadb-perl-1.22/t/testdb/mysql.pid --explicit_defaults_for_timestamp --skip-networking

The most urgent question is whether this is a MariaDB regression that
should result in excluding 1:11.8.8-0+deb13u1 from the point release.

cu
Adrian

On 08 juil. 2026 12:36, Adrian Bunk <bunk@debian.org> wrote:

[...]

Bad idea to have 11.8.8 to stable. This version is broken, even if
MyhTV isn't in debian :

https://forum.mythtv.org/viewtopic.php?p=31030

https://www.deb-multimedia.org/lurker/message/20260707.153854.696f4834.en.html

Christian

Hi Gregor,

I noticed you pushed a commit to
https://salsa.debian.org/perl-team/modules/packages/libdbd-mariadb-perl/-/commits/master
two weeks ago and saw that the post-build tests started to fail. Did
you investigate the failures?

Do you see what is the root cause to these failing?

not ok 140 - NoChopBlanks: c_text should not have blanks chopped
not ok 141 - NoChopBlanks: c_tinytext should not have blanks chopped
not ok 142 - NoChopBlanks: c_mediumtext should not have blanks chopped
not ok 143 - NoChopBlanks: c_longtext should not have blanks chopped
not ok 144 - NoChopBlanks: b_blob should not have blanks chopped
not ok 145 - NoChopBlanks: b_tinyblob should not have blanks chopped
not ok 146 - NoChopBlanks: b_mediumblob should not have blanks chopped
not ok 147 - NoChopBlanks: b_longblob should not have blanks chopped
...
not ok 11
...
Test Summary Report
-------------------
t/50chopblanks.t (Wstat: 2048 (exited 8) Tests: 180 Failed: 8)
Failed tests: 140-147
Non-zero exit status: 8
t/rt118977-zerofill.t (Wstat: 256 (exited 1) Tests: 12 Failed: 1)
Failed test: 11
Non-zero exit status: 1
Files=94, Tests=4136, 54 wallclock secs ( 0.77 usr 0.19 sys + 9.22
cusr 1.91 csys = 12.09 CPU)
Result: FAIL
Failed 2/94 test programs. 9/4136 subtests failed.


Clearly this is related to some change in libmariadb3 from 11.8.8 but
we would need find out some more details to be able to poinpoint what
change it was, or at least have enough data to file a bug upstream. I
was wondering if you were already aware of something as you saw the
build failure some weeks ago.

Hi!

I added the new test failures to d/changelog. And then I looked
around a bit but didn't find anything, sorry …


Cheers,
gregor

Seems this is tracked upstream as https://jira.mariadb.org/browse/CONC-821

Seems that current state of this issue is that the PR by Daniel Black
at https://github.com/mariadb-corporation/mariadb-connector-c/pull/317
got initial review from Georg Richter, and is now pending Daniel to
respond. I will wait 24h and then take latest version of that PR and
add as emergency patch on top of 11.8.8 in Debian.

Hi, any news here?

libdbd-mariadb-perl is currently uninstallable in sid, because it needs
a rebuild for Perl 5.42. AIUI that rebuild can't be done before this
bug is fixed (or worked around somehow.)

Hi,

I am waiting for upstream to fix this and/or communicate how they
intend to fix this in https://jira.mariadb.org/browse/CONC-821. I was
also looking at what Fedora is doing and they seem to be waiting for
upstream to resolve this first too, as we downstream dont't want to
end up with permanent diversion from upstream.

Hi,

MariadB 11.8.9 has been uploaded to Debian unstable. According to
https://jira.mariadb.org/browse/CONC-821 it has a commit that fixes
the issues that broke MythTV, Perl and more.

Does anyone have an easy test case at hand to verify if the issue was fixed?

I have been reviewing the original faulty change
https://github.com/mariadb-corporation/mariadb-connector-c/commit/0fb69426d13c14cb6af5ceb0dd9ae9d2777abea8,
the fix in Fedora
https://src.fedoraproject.org/rpms/mariadb-connector-c/raw/03b2e1d2171f33529383f462e64fb0c8fe0812db/f/conc-821-fix-bind-result-length.patch
and the fix in MariaDB
https://github.com/mariadb-corporation/mariadb-connector-c/commit/40806da9
but I am unable to  deduce if the original regression was properly
fixed or not.

The original bug report was about libdbd-mariadb-perl 1.22-1 failing
two of its tests:

Test Summary Report
-------------------
t/50chopblanks.t                      (Wstat: 2048 (exited 8) Tests: 180 Failed: 8)
   Failed tests:  140-147
   Non-zero exit status: 8
t/rt118977-zerofill.t                 (Wstat: 256 (exited 1) Tests: 12 Failed: 1)
   Failed test:  11
   Non-zero exit status: 1

So just building libdbd-mariadb-perl and checking the test results
sounds like a good start :)

* A few minutes later *

Doesn't look good:

Test Summary Report
-------------------
t/50chopblanks.t                      (Wstat: 2048 (exited 8) Tests: 180 Failed: 8)
   Failed tests:  140-147
   Non-zero exit status: 8
t/rt118977-zerofill.t                 (Wstat: 256 (exited 1) Tests: 12 Failed: 1)
   Failed test:  11
   Non-zero exit status: 1



Cheers,
gregor

I've just installed libmariadb3 11.8.9+ds-1 from unstable on my MythTV
system running 1:36.0+fixes20260801.git0d26328-dmo1, and MythTV works
fine: recordings take place and upcoming recordings are scheduled
normally.

Downgrading to libmariadb3 11.8.8-1 in testing breaks everything.

So, from the MythTV perspective, it looks as though the new MariaDB
11.8.9 packages should be safe to install for MythTV users. I'll
update if I notice any issues over the next day(s).

Hello!

Am Di, Sep 01, 2026 at 22:27:06 +0300 schrieb Otto Kekäläinen:

According to Nick Morrott on dmo-discussion@deb-multimedia.org
(message-id
<CAOQWjw1=hg19fjBCK1YCSwxu8A5Kzdqs5wKioYtN2h-VvvwsCw@mail.gmail.com>) is
the MythTV problem fixed.

Many greetings,

	Stephan

Hello,

Bug #1139473 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/93f7c6d1b65a1d58b5259815d83a02f8fb463a17

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1139473

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 1139473@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: Fri, 04 Sep 2026 19:19:19 +0000
Source: mariadb
Architecture: source
Version: 1:11.8.9+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>
Changed-By: Otto Kekäläinen <otto@debian.org>
Closes: 1139473 1141671 1144671 1146585
Changes:
 mariadb (1:11.8.9+ds-2) unstable; urgency=medium
 .
   * Add missing --version_cc to the custom `mariadb_config` (Closes: #1146585) *
   * Backport upstream patch to fix upstream CONC-821 about
     mysql_stmt_bind_result zeroes *length for temporal result columns which
     broke among others Perl, Python, MythTV and more
     (Closes: #1139473, #1141671, #1144671)
   * Extend test skip lists after witnessing frequent sporadic failures on armhf
Checksums-Sha1:
 8f8382cfc19a3c8732d15740a4c6b7f2a2ac4e87 5396 mariadb_11.8.9+ds-2.dsc
 47eac511ec1d2083ccc7f971e9eeea9248095fe3 304768 mariadb_11.8.9+ds-2.debian.tar.xz
 976b725d92535059aa16ea7f7b535031703cfb18 13742 mariadb_11.8.9+ds-2_source.buildinfo
Checksums-Sha256:
 fa3c4609a709d6f1012b48940a6567bc534f3335512f2daa8b9a7f4a4072ab9e 5396 mariadb_11.8.9+ds-2.dsc
 baf5361d53d926f85e3da10ad79172d9130d911daefdd1f86ef868c86d7a1970 304768 mariadb_11.8.9+ds-2.debian.tar.xz
 4689efb57aac0fa35e01570f5a20c64ded3a350cdf541d2a7647bd2b5bf9628d 13742 mariadb_11.8.9+ds-2_source.buildinfo
Files:
 aa87da2e4c5c70f21928354d5d7a6b2a 5396 database optional mariadb_11.8.9+ds-2.dsc
 0df9285bad0fb8c88668bb84a748b155 304768 database optional mariadb_11.8.9+ds-2.debian.tar.xz
 b93bfc4afb436fe7c7513776125a8f15 13742 database optional mariadb_11.8.9+ds-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAmqdCOUACgkQvthEn87o
2oiH8w/8Dy/DtCfxeOdugnDBLSTIYdwlnYWxlW7t/goxYqzkC52eXCoOqoP+gFWW
mnMb4DMjMZXiu7kgVJmrtWqJABTmZLXv04dPqbP2CzUOol7hxxPEy0ylJ+RiiLzH
xzYtFO0+qLwv/4gE4LcyYt+XaB7nN6G8EQtKYg77/uz94/YI6uHIoo36cAiNRN2E
43iyTBAC4qhHwd+EAgBEZaWadCI9M8nb9uQfWNnzoIJ1GZ70LdIHQmwjlBgPljqu
u5R29wKZ5sHKai2nSfp25AWlfwy2lC8O1d4DRN/MzDo/VlkTejx+pzhTFo+kk7jU
WC3AV9E+qcLYNZCKmp0HGMQLr/eomgl+g06MCNfucjrFnjA/1/cRvm/oV9/z8q20
p8TeLo1xYUV0LMfP5YDKsaJdQQWaLhQhxFTo8LhdGLZspYbb0u2wAEpieew3XtSk
bMWcXV+5vn20Dl9wFSo80vSCgkTAKviQd72wFfuSRm23AI2my44HmH9ZRtAC2qKg
XIJSn1sSPYuZpHO3HqtFPEtu2o7JqLXT6DXg8Em9hgEUlUG1PGjHLQsI5E7Yv7FU
beJIH5UHOwAmhv+USXhyKOvBLfI/XGEu5AXC7kmGaGOqOtNC1gvDwpq0IYe788ws
Sol8OomcIy1ewP/Ab3L81adj4cSP1ugN+KdTp/9Qld4IgkkAPLQ=
=ioS6
-----END PGP SIGNATURE-----

The latest 1:11.8.9+ds-2 contains a patch that fixes the Perl build
issue. I tested it locally before uploading and now also reran
https://salsa.debian.org/perl-team/modules/packages/libdbd-mariadb-perl/-/pipelines/1162965
that confirms build works again.

Excellent, thank you!


Cheers,
gregor