Your message dated Mon, 6 Mar 2023 23:33:16 -0800 with message-id <CAOU6tACtTx=efY6M3e9bGvPcjra+8yYJ+nhw=g_7vu0uao8...@mail.gmail.com> and subject line Re: [debian-mysql] Bug#1018063: Regression: mariadb client default charset changed breaks compatibility has caused the Debian Bug report #1018063, regarding Regression: mariadb client default charset changed breaks compatibility to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1018063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018063 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mariadb-client Version: 1:10.5.15-0+deb11u1 Apparently as a fix for Bug #933063 the default charset in Bullseye for clients using libmariadb.so.3 was changed from latin1 to utf8mb4. This breaks compatibility with all clients relying on the default behaviour. This should not happen and diverges from upstream for (at least to me) no apparent reason. I could not find prior mention in the changelog why the default should be utf8mb4 in the first place. Anyways: The following perl script illustrates the issue: use DBI; my $dbh = DBI->connect("dbi:mysql:"); my $sth = $dbh->prepare("show variables like '%character_set_client%'"); $sth->execute(); printf "%s: %s\n", $sth->fetchrow_array(); On Buster: # LD_PRELOAD=./libmariadb.so.3.buster perl test_cs.pl character_set_client: latin1 On Bullseye: # LD_PRELOAD=./libmariadb.so.3.bullseye perl test_cs.pl character_set_client: utf8mb4 Again: this seems to me like a breakage of user expectations when upgrading buster -> bullseye. And while I know that this horse has probably left the barn, I would like to suggest reversing the default to the upstream/Buster value. In addition to this issue the implementation seems incomplete. If you explicitly set the the default like so: use DBI; my $dbh = DBI->connect("dbi:mysql:“); $dbh->do("set names default“); # HERE my $sth = $dbh->prepare("show variables like '%character_set_client%'"); $sth->execute(); printf "%s: %s\n", $sth->fetchrow_array(); The result is # LD_PRELOAD=./libmariadb.so.3.bullseye perl test_cs.pl character_set_client: latin1 Which means explicitly and implicitly using defaults yields different results. Debian Release 11.4 libmariadb.so.3.buster 1:10.3.34-0+deb10u1 libmariadb.so.3.bullseye 1:10.5.15-0+deb11u1
signature.asc
Description: Message signed with OpenPGP
--- End Message ---
--- Begin Message ---Hi! Latest version of MariaDB in Debian unstable/testing/Bookworm is 10.11.2. You might want to consider testing it. If you want to contribute in the open source way to fix this or any other issue, see https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian on how to submit a Merge Request! If you have time to help, please consider these (in order of importance): 1. Review current open MRs at https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests 2. Review items highlighted by Debian QA systems (Lintian, builds etc) and submit a fix to improve the quality: https://tracker.debian.org/pkg/mariadb 3. Review what testing we have at https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines and think about potential gaps - CI is very important as it is the only way we can prevent regressions in a scalable way 4. Review/follow-up on existing bugs that currently need more information: https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=mariadb&src=mariadb-10.6&src=mariadb-10.5&src=mariadb-10.3&src=mariadb-10.1 MariaDB and C++ skills are useful, but not required. For example reviewing the NEWS for 10.11 requires no coding skills: https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/37 My request for help from debian-devel in https://lists.debian.org/debian-devel/2023/02/msg00272.html did not get many responses, so the future of this package depends on how active the users and people who previously reported bugs are in participating in the maintenance of the package. - Otto
--- End Message ---
