Hi, This bug is likely invalid/won't fix.
The ability to run MariaDB in 2038 and beyond is tested and state documented in https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/74 The failures in the log you provided at https://people.debian.org/~sanvila/build-logs/ftbfs-future/mariadb_11.8.5-4_amd64-20260205T130203.893Z show two upstream tests fail due to test hard coded to check something after 2030-01-01. These are trivial to fix and upstream most likely fixes them once 2030 is a bit closer. main.long_unique_bugs w1 [ fail ] Test ended at 2030-08-09 12:32:50 CURRENT_TEST: main.long_unique_bugs --- /<<PKGBUILDDIR>>/mysql-test/main/long_unique_bugs.result 2025-11-13 08:45:29.000000000 +0000 +++ /<<PKGBUILDDIR>>/mysql-test/main/long_unique_bugs.reject 2030-08-09 12:32:49.976239090 +0000 @@ -62,8 +62,8 @@ select pk, f, row_end > DATE'2030-01-01' from t1 for system_time all; pk f row_end > DATE'2030-01-01' 1 foo 1 -1 foo 0 -1 bar 0 +1 foo 1 +1 bar 1 drop table t1; # # MDEV-18747 InnoDB: Failing assertion: table->get_ref_count() == 0 upon dropping temporary table with unique blob Result content mismatch main.mysqldump w1 [ fail ] Test ended at 2030-08-09 12:33:03 CURRENT_TEST: main.mysqldump mysqltest: At line 2075: query 'DROP EVENT ev1' failed: ER_EVENT_DOES_NOT_EXIST (1539): Unknown event 'ev1' The result from queries just before the failure was: < snip > CREATE TABLE t1 (f1 INT); CREATE TRIGGER tr1 BEFORE UPDATE ON t1 FOR EACH ROW SET @f1 = 1; CREATE PROCEDURE pr1 () SELECT "Meow"; CREATE EVENT ev1 ON SCHEDULE AT '2030-01-01 00:00:00' DO SELECT "Meow"; Warnings: Note 1588 Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation
