On Wednesday, 1 March 2023 17:09:54 CET Otto Kekäläinen wrote: > > > 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.
Sorry, I can only really report how the bug arose on my system. Reproducing it would presumably involve creating an environment where Akonadi is initialised and then trying to access resources via Akonadi. Without some kind of test suite, which I presume does not already exist for Akonadi, that would potentially be a lot of work. > > https://github.com/mariadb-corporation/mariadb-connector-c/commit/d204e831 > > 04222844251b221e9be7eb3dd9f8d63d > Thanks for pointing this one. I was reading the commit > https://github.com/mariadb-corporation/mariadb-connector-c/commit/a37b7c3965 > 706f9a062baaba0c494dd6efb2c306 that another reporter posted earlier. Yes, it is difficult to navigate to the commit on the appropriate branch, and the involvement of mysql_get_client_info in that patch also confused me. > > > However, as a clear patch was suggested I did it in > > > https://salsa.debian.org/mariadb-team/mariadb-10.3/-/commits/bugfix/1031 > > > 863-> 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/292377544983e0db > 9b702399a977b900cdacbcee is building. Thank you for activating this again. Paul
