Comment 12 for bug 1814258

Hi Otto,

Okay, I'm going to hold off on publishing the mariadb-10.0 updates until some confirmation that they have been tested.

For mariadb-10.1, I checked the build time tests, and they looked okay, so I went ahead and published that package, which is why it's not showing up in the excuses page. The autopkgtest failure log is at https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-ubuntu-security-proposed-ppa/bionic/amd64/m/mariadb-10.1/20190207_122932_ab116@/log.gz (at least for the time being) if you want to look at it directly.

If it does get reaped, the relevant bits of the log are as follows:

  Removing autopkgtest-satdep (0) ...
  autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs
  Reading package lists...
  Building dependency tree...
  Reading state information...
  E: Unable to locate package mariadb-test
  upstream FAIL badpkg
  blame: mariadb-10.1
  badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
  autopkgtest [12:29:22]: @@@@@@@@@@@@@@@@@@@@ summary
  smoke PASS
  upstream FAIL badpkg
  blame: mariadb-10.1

In particular, note the "E: Unable to locate package mariadb-test" message. The mariadb-10.1 control file does not build a mariadb-test package.

Thanks.