[debian-mysql] mariadb-10.3 debci failure with with britney triggered perl builds

Otto Kekäläinen otto at debian.org
Wed Jun 5 07:57:30 BST 2019


Hello!

I was just about to uplaod mariadb-10.3 release 1:10.3.15-2 to fix the
RocksDB/s390x autopkgtest failure when I noticed that yesterday the
debci started to fail:

https://ci.debian.net/packages/m/mariadb-10.3/unstable/amd64/
perl/5.30.0-1 bubblewrap/0.3.3-1 cpulimit/2.6-1
libmodule-corelist-perl/5.20190522-1 libwebsockets/2.4.2-1
silkaj/0.6.5-2 stunnel4/3:5.54~b3-1 systemd/242-1

Log https://ci.debian.net/data/autopkgtest/unstable/amd64/m/mariadb-10.3/2453744/log.gz
shows failures in:

************
The following packages have unmet dependencies:
 autopkgtest-satdep : Depends: mariadb-plugin-rocksdb but it is not installed or
                               mariadb-server-10.3 but it is not installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be
caused by held packages.
E: Unable to correct dependencies
...
Broken mariadb-server-10.3:amd64 Depends on libdbi-perl:amd64 < none |
1.642-1+b1 @un uH >
  Considering libdbi-perl:amd64 2 as a solution to mariadb-server-10.3:amd64 0
  Holding Back mariadb-server-10.3:amd64 rather than change libdbi-perl:amd64
************

The britney triggered build ran on amd64 so this is not a duplicate of
the recent autopkgtest/rocksdb fixed in
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/0b17f717f91365c4cf37dd88b565e7ee8a031955
but maybe related.

I am not quite sure what conclusions to draw from that debci log.

Autopkgtest on a test run in
https://salsa.debian.org/mariadb-team/mariadb-10.3/pipelines today
still passed.

Can somebody here help?



More information about the pkg-mysql-maint mailing list