On Fri, 2020-11-27 at 14:05 +0200, Otto Kekäläinen wrote: > > 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?
Well, we can consider it, but it would certainly be unconventional. If the packages from buster will work without issues on unstable and testing though, it's not a particular inconvenience and doesn't require any action on your part. (I don't know if they will, but I'd hope that if they're installable then they would work.) In any case, this issue exists already with 10.3.25, so don't let it stop you from getting 10.3.27 uploaded. Regards, Adam
