Hello! > > Please unblock package galera-4 to fix MariaDB upgrade as reported in > > #988089. > > I appreciate a fix for that bug, but did you really have to do that by > uploading a new upstream release too? How is the new upstream release > related to that bug?
Yes, the upstream package is a maintenance/fix release for Galera 4 that does not introduce any new features, only fixes bugs. It is the kind of change that could go into Debian Bullseye as a stable update too, so I thought it would be better to do it now. > > [ Risks ] > > Low, leaf package. > > Nope, the package is a key package. Indeed, it seems to be listed at https://udd.debian.org/cgi-bin/key_packages.yaml.cgi However, only MariaDB depends on it and the package is very small and has traditionally had zero or almost zero bugs in Debian. I would argue that including it now is a very safe thing to do. It has also been well tested. > > This also introduces the latest upstream version. It has already been > > in Sid for a while without reported regressions, and in general Galera > > packages have been very low on regressions. > > But that is totally not in line with our freeze policy [1][2]. Please > revert the upstream release while fixing 988089. I beg you to reconsider, as the new upstream release is a bugfix-only release that would be uploaded post-Bullseye in a stable update anyway. Having these bugfixes in Bullseye is a service to our users and very low risk, and thus hopefully justifiable during hard freeze.
