Hi Otto, Otto Kekäläinen wrote on 28/05/2020: > A future version of MariaDB might have the charsets in its own > directory, but we can't start changing paths of stuff in existing > stable releases, such as MariaDB 10.3 in Ubuntu 20.04 or Debian > Buster. If MySQL introduces a backwards incompatible change, the new > uploads should test for them and work around issues discovered. > > In MariaDB we are building python-mysql against libmariadb on every > commit in the CI to ensure nothing is broken: > https://salsa.debian.org/mariadb-team/mariadb-10.3/pipelines > > If you think MythTV has something unique about this, we could add > MythTV builds to the CI to ensure new uploads of MariaDB does not > break MythTV builds in Debian?
I don't think there's anything special about MythTV, in my understading it's just how some users happened to hit the problem. I hit it in a completely different way: as a failure in an autopkgtest of libdbd-mariadb-perl. I have not much to add to your analysis, and I agree in that we can't and shouldn't change the structure of the packages in existing stable releases. However we can take this issue as a good warning on the fact that compatibility between the two DBs can't be assumed, and the packages in the development releases should start taking this into account. Cheers, Paride
