> I am in favour of removing galera-4 from Depends and as suggested by > Olaf make it only a suggestion (Suggests), I am not sure if it's even > necessary (after all, MariaDB standalone server and Galera cluster are > two very different setup).
Yes we consider doing that. Note however that it does not fix this bug in question, we still want the dist-upgrade for Galera users to succeed. It also needs to be debugged and a MR submitted on how to change Galera-4 debian/control file for the upgrade to pass flawlessly. > The salsa CI is still green when doing so: > https://salsa.debian.org/faust/mariadb-10.5/-/pipelines/254990 Good. Did you also test upstream buildbot? > Finally, galera-4 is not a dependency on RPM: > | docker run fedora:latest bash -c "yum update -y && yum install > mariadb-server -y && rpm -qa | egrep 'mariadb|galera'" Good point. I digged into git blame and found out that I actually tried to make galera-3 a recommends in 2015 but reverted because upstream tests started failing: Starting point: Depends: galera https://github.com/MariaDB/server/commit/df4dd593f29aec8e2116aec1775ad4b8833d8c93#diff-70229a6b99c9cf63c053270b10c80d7fe50c33c7c167f7c1a4d84a093334d65bR195 Change: https://github.com/MariaDB/server/commit/6bd94cf54274d54521ece1e50d534777122ff29e Revert: https://github.com/MariaDB/server/commit/6bd94cf54274d54521ece1e50d534777122ff29e But as said, the bug #988089 can only be fixed by a change in galera-4 debian/control. Changing the mariadb-10.5 debian/control to recommends:galera-4 is a separate change.
