[debian-mysql] Bug#990708: mariadb-server-10.5: upgrade problems due to galera-3 -> galera-4 switch

[Otto Kekäläinen]

> Thanks for clarifying. That was not obvious since the filename of the
> plugin library did not change. And another reason that dropping the
> virtual galera package should not do any harm.
> (If the plugin would have changed the name (e.g. used a proper
> SOVERSION), -3 and -4 should be co-installable and we would not have
> this problem now.) Actually, I don't really like calling it "plugin" any
> more. (A probably good example of packaged plugins would be proftpd*.)

Ideally, yes. Filed https://github.com/codership/galera/issues/599 so
we don't forget this.

> PS: Otto, what do you think about dropping the epoch from
> src:mariadb-10.6 onwards and applying it only to the binary packages
> that don't change their names? If you want to do this, get in touch once
> you start preparing 10.6

Seems a bit messy to have the epoch in some packages but not all. Also
if we want to start doing this, it would need to start with MariaDB
10.7 and be done both upstream and in Debian so that they stay in sync
and we don''t end up with users "upgrading" from MariaDB 10.6 from
Debian.org repos to MariaDB 10.5 in MariaDB.org repos.