Hello! As part of our CI we run a Bullseye MariaDB 10.5 to Debian Sid MariaDB 10.6 upgrade on every commit. If passes correctly with:
The following packages will be REMOVED: mariadb-client-10.5 mariadb-client-core-10.5 mariadb-server-10.5 mariadb-server-core-10.5 The following NEW packages will be installed: libdaxctl1 libkmod2 libndctl6 libnuma1 libodbc2 libodbccr2 libpcre2-posix3 libpmem1 liburing2 mariadb-client-10.6 mariadb-client-core-10.6 mariadb-server-10.6 mariadb-server-core-10.6 To continue with solving this issue I would like to first get it reproduced in the CI. The root cause why we have an upgrade issue is that there is a scenario users can hit that is not covered by our CI. Fixing that would ensure proper testing coverage and forever working MariaDB upgrades. Latest CI run: https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines/350897 Bullseye to Sid upgrade test: https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/2492192 Source. https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/salsa-ci.yml How to contribute: https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian
