On 05/07/2021 21.20, Otto Kekäläinen wrote:
Hello!
I was able to reproduce this, and addressed it in
https://salsa.debian.org/mariadb-team/galera-4/-/commit/27a142792b5e02e66b8f1adf9a7b896c5722dd17
+ added Salsa-CI testing for this specific scenario so that it would
not regress again, but seems there is still some second scenario that
does not upgrade properly.
I wish somebody could contribute with exact steps on how to reproduce
the issue. So far I've gotten some half attempts at that but they
haven't been actionable for me.
I'm currently looking at upgrading roundcube-core in a minmal chroot
with --install-recommends *DISABLED* ...
My plan was to keep Galera-3 in Debian stable / Ubuntu stable as for
the duration that MariaDB 10.3 is supported upstream, as MariaDB does
not offer Galera by themselves, so it is better to have it available
in distro.
How would one use galera-3 in bullseye? There is no mariadb-10.3 in
buster, only 10.5 which depends on galera-4 which blocks galera-3 from
being installed.
(Even if galera-3 gets removed from bullseye, it will stay in buster
(and sid if you want))
What do you need the virtual galera package for? My gut feeling is that
this is the source of our problems because it forms some kind of a
conflicts cycle.
Andreas
