[debian-mysql] Bug#1018063: Bug#1018063: Regression: mariadb client default charset changed breaks compatibility

[Otto Kekäläinen]

Control: -1 tags wontfix

Hello Tim, Faustin and Georg!

Tim: The choice of utfmb4 was made also at upstream, but you are
right, Debian adopted it earlier than upstream and thus diverged
slightly. In the next version in Debian (MariaDB 10.6) this is again
in sync with upstream.

> > Issues: CONC-547, MDEV-25485.
> > Github discussion:
> > https://github.com/MariaDB/server/pull/1722#issuecomment-821027426
>
> @Otto, since you are involved in PR1722 you could probably explain what
> the plans for Debian packaging are with respect to charset?

There are no special plans.

The rules file defines utf8mb4 as default charset:
-DCONC_DEFAULT_CHARSET=utf8mb4
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/blob/bullseye/debian/rules#L94

This was implemented in
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/ca5e93c754209f9c1a729bb057332ab3b0b76363
and we even have the Salsa-CI to ensure that we don't regress back to
latin1 anymore.

The libmariadb.so.3 in MariaDB 10.3 is of a different version and
built with a different server, so it might be slightly different. The
ABI itself should however be backwards fully compatible.