Since this is now the first time I noticed that new time_t should be available for testing and I started testing, I noticed that MariaDB has built-in check to prevent it from running on 2038 at all:
# date Thu Mar 3 05:55:28 UTC 2039 # ./sql/mariadbd --version 2039-03-03 5:58:55 0 [ERROR] This server doesn't support dates later than 2038 Seems to stem from This is due to https://github.com/MariaDB/server/blob/11.5/sql/mysqld.cc#L3903-L3908 I am looking into this now as well.. On Sat, 2 Mar 2024 at 16:41, Otto Kekäläinen <o...@debian.org> wrote: > > > > Could you Sebastian perhaps quickly skim through the commit that > > > implemented this > > > https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/8194544349982990fb2585c2a8c15c4db3904735 > > > and say if there might be something else missing as well? > > > > Did you mean > > https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/d2a0784f1e01b6613fefda17199a4e9867a126c3? > > > > At least for now that looks good. > > No I meant the original one, but you have now seen the original and > amendment and had no further comments, so seems good. > > I see Steven just uploaded curl 8.6.0-3.2 to fix the curl issues. I > will continue to wait a bit for the basic dependencies to stabilize, > for example this seems to affect many packages: > > libnsl2 depends on: > - libtirpc3:armel (>= 1.0.2) > libtirpc3t64 conflicts with: > - libtirpc3:armel (< 1.3.4+ds-1.1) > > I will upload new MariaDB as soon as I can verify that it is buildable.