Hi Otto, On 06/01/2019 16:08, Otto Kekäläinen wrote: > Hello! > > I just realized that the upload of mariadb-10.3 into Debian includes > the following transitions: > - libmariadbd18 -> libmariadbd19 > - libmariadbclient18 becomes deprecated and fully replaced by the > libmariadb3 library already in Debian for a longer time (source > package mariadb-connector-c)
Someone created https://release.debian.org/transitions/html/mysql-default.html to track this. > Technically this can constitute a transition and I have not followed > the process desrcibed at: > https://wiki.debian.org/Teams/ReleaseTeam/Transitions > > My priority has been in packaging mariadb-10.3 so we would not be > stuck with mariadb-10.1 in buster. It is a very large package and this > transition was just a smal part of it, and I realized it too late. > > My focus was mostly on if I manage to pull this off at all in time, > and I overlooked planning this transition detail. Sorry! > > Luckily there has not been any major problems so far. The Salsa-CI, > ci.debian.net etc are all looking good. There is maybe just one issue > that can be hard to tackle, details in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917303 https://packages.qa.debian.org/m/mariadb-10.3.html points to an autopkgtest failure on pam-mysql too, though that one doesn't seem to have a corresponding bug report yet. Cheers, Emilio
