(Replying with bug included so this gets recorded.) I don't have any solution on my mind. I think mariadb-upgrade should automatically handle this. If it does not, a bug should filed upstream.
On Thu., May 21, 2026, 22:32 Viktor Matys, <[email protected]> wrote: > Hi, > > yes these bug reports looks very similar to mine. > > I've upgraded according to apt/history.log: > > *mariadb-server:amd64 (1:10.11.14-0+deb12u2, 1:11.8.6-0+deb13u1)* > > I did some exploration and found workaround by setting variables in > 50-server.cnf: > > collation_server = utf8mb4_general_ci > character_set_collations = utf8mb4=utf8mb4_general_ci > > Which set the behavior back to mariadb 10 and the dump --system=users > works without errors. > > But this doesn't solve upgrading to the new collation > name utf8mb4_uca1400_ai_ci. > > I'd appreciate mentioning this issue in release notes and in upgrade > manual to be prepared for it :) > > Thank you for your big effort. If you need some another info from me, ask > please. > > Regards, > > Viktor > > On 2026-05-21 10:19, Otto Kekäläinen wrote: > > Hi, > > Are you perhaps running into > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104533 or > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126850? > > What is the MariaDB version exactly you updated from and to? > >
