> > The fact that his issue surfaced now about something that changed in > > Debian 1-2 years ago and was changed upstream 2 years ago confuses me. > > Also I don't have any easy way to fire up a container and reproduce > > the issue. > > It isn't really so mysterious, and I tried to explain it in the original bug I > filed against Kontact:
i was referring to steps to reproduce. > https://github.com/mariadb-corporation/mariadb-connector-c/commit/d204e83104222844251b221e9be7eb3dd9f8d63d Thanks for pointing this one. I was reading the commit https://github.com/mariadb-corporation/mariadb-connector-c/commit/a37b7c3965706f9a062baaba0c494dd6efb2c306 that another reporter posted earlier. > > However, as a clear patch was suggested I did it in > > https://salsa.debian.org/mariadb-team/mariadb-10.3/-/commits/bugfix/1031863-> > > libmariadb3-version-id > .. > It seems that the pipeline failed, but I managed to build a revised package > anyway. Salsa-CI is back online and https://salsa.debian.org/mariadb-team/mariadb-10.3/-/commit/292377544983e0db9b702399a977b900cdacbcee is building.
