Bug#975837: buster-pu: package mariadb-10.3 10.3.27-0+deb10u1
> As previously discussed, as things stand, in order to include this
> update in the point release we will also need to copy it to testing and
> unstable either during, or before, the point release, to avoid version
> skew.
This is outside the domain of my expertise, but just to be sure: there
cannot be any new mariadb-10.3 uploads to unstable/testing anymore as
the packages from it would conflict with mariadb-10.5.
MariaDB 10.5 finally landed in testing yesterday, and I plan to file a
removal request in 1-2 weeks once the "dust has settled", so maybe no
syncing is needed and we can avoid excess inconveniences?
Reply to: