autopkgtest always fails with "I can't find mariadb-test"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mariadb-10.1 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bionic |
Fix Released
|
Medium
|
Dan Streetman | ||
Cosmic |
Fix Released
|
Medium
|
Dan Streetman |
Bug Description
[impact]
mariadb-10.1 autopkgtests always fail because it can't find its dependency 'mariadb-test'
[test case]
see any of the mariadb-10.1 autopkgtest logs, or just run autopkgtest on mariadb-10.1
[regression potential]
very low, as no actual code changes are involved; only debian/ content is changed, and that is limited to adding the -test packages back to the control file, restoring mariadb-test package setup, adding unstable-test lists, and adding isolation-container requirement to the smoke test. All have been cherry-picked from debian.
Any regressions would almost certainly result only in failed tests and/or builds.
[other info]
this has been failing for quite a while now. it is failing only for bionic and cosmic; disco has corrected it. The problem is that debian removed the mariadb-test packages from 10.1 because they added 10.2, which also provided the packages into the same namespace (the binaries don't have the -10.1 suffix). However, we don't provide 10.2 in bionic or cosmic, and removing the 10.1 tests only results in 1) no upstream tests being runnable and 2) since we didn't remove the mariadb-test depends in debian/
There is also a more serious matter, that bionic has continued to get mariadb-10.1 updates, while cosmic has not. So the bionic version is higher than the cosmic version:
$ rmadison mariadb-10.1
mariadb-10.1 | 1:10.1.29-6 | bionic/universe | source
mariadb-10.1 | 1:10.1.29-6ubuntu2 | cosmic/universe | source
mariadb-10.1 | 1:10.1.
mariadb-10.1 | 1:10.1.
Changed in mariadb-10.1 (Ubuntu): | |
status: | New → Fix Released |
description: | updated |
description: | updated |
Changed in mariadb-10.1 (Ubuntu Cosmic): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in mariadb-10.1 (Ubuntu Bionic): | |
assignee: | nobody → Dan Streetman (ddstreet) |
status: | New → In Progress |
Changed in mariadb-10.1 (Ubuntu Cosmic): | |
status: | New → In Progress |
importance: | Undecided → Low |
Changed in mariadb-10.1 (Ubuntu Bionic): | |
importance: | Undecided → Medium |
Changed in mariadb-10.1 (Ubuntu Cosmic): | |
importance: | Low → Medium |
Changed in mariadb-10.1 (Ubuntu): | |
importance: | Undecided → Medium |
An upload of mariadb-10.1 to cosmic-proposed has been rejected from the upload queue for the following reason: "The SRU carries backports of security-updates up to 10.1.38. Seeing that those were security updates this might be still good for an SRU, but pulling those into cosmic through a separate pocket without a tracking bug seems like a bad idea. Security updates are usually checked for regressions by the security team - here, since the security team is not directly involved, we need to have a way to track issues regarding backporting a new upstream version. Please include a tracking bug for the upstream backport (one bug is enough) and re-submit. Thanks!".