Hello! ma 7. tammik. 2019 klo 10.38 Otto Kekäläinen (o...@debian.org) kirjoitti: > > ma 7. tammik. 2019 klo 11.20 Emilio Pozuelo Monfort (po...@debian.org) > kirjoitti: > .. > > 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. > > That's right, there is no bug report about it but there should > probably be for easier tracking. > > In discussions on the mailing list the pam-mysql maintainer says a > binNMU will likely fix it: > https://alioth-lists.debian.net/pipermail/pkg-mysql-maint/2019-January/012547.html
Status update here: - pam-mysql fixed via rebuild - libdbd-mysql-perl fixed upstream and latest release 4.050-1 uploaded to unstable and CI passes: https://ci.debian.net/packages/libd/libdbd-mysql-perl/ - mariadb-10.3 still failing on libdbd-mysql-perl release 4.049-1 and thus not entering testing https://tracker.debian.org/pkg/mariadb-10.3 - mysql-defaults not entering testing since pending for mariadb-10.3 first - libdbd-mysql-perl not entering testing since pending for mysql-defaults first What do you advice to do at this point as there is only one day deadline to the transition freeze? If I re-upload mariadb-10.3 with libmariadbclient18 having the following Breaks: libpam-mysql (<< 0.8.1-1+b1), libdbd-mysql-perl (<< 4.049-1.0), Then it will help with the transition but a re-upload will reset the counters and thus miss the transition deadline by 2-3 days.
