Op za 22 mei 2021 om 23:30 schreef Otto Kekäläinen <o...@debian.org>: > > Hello! > > On Sun, May 16, 2021 at 4:18 PM Otto Kekäläinen <o...@debian.org> wrote: > > > > > >> > 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. > >> Ok but I have no idea how this should be handled then. > > > > > > I outlined the exact galera-4 debugging steps in my email on May 13th. The > > solution can be found and also tested/validated easily with those steps. > > I had some spare time today and followed those steps, resulting in > this MR: https://salsa.debian.org/mariadb-team/galera-4/-/merge_requests/5
Thanks a lot! > Would somebody like to review/test it? Conflicts: galera, galera-3, ... Breaks: galera, galera-3 > When one binary package declares a conflict with another using a Conflicts > field, dpkg will refuse to allow them to be unpacked on the system at the > same time. This is a stronger restriction than Breaks, Based on the text I'd assume it doesn't make sense to have a package in both conflicts and breaks. Am I reading the text wrong? https://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts -- Olaf
