[debian-mysql] Bug#882681: mariadb-10.1: Missing mariadb-test package prevents testing migration

[Andreas Metzler]

Control: severity -1 normal
Control: tags -1 moreinfo

On 2017-11-25 Bas Couwenberg <sebastic at xs4all.nl> wrote:
> Source: mariadb-10.1
> Version: 1:10.1.29-6
> Severity: serious
> Justification: makes the package in question unusable or mostly so
> Control: affects -1 src:apr-util src:asterisk src:dovecot src:exim4 src:gammu src:gdal src:gnunet src:gnustep-sqlclient src:grass src:jabberd2 src:kamailio src:kdb src:kopanocore src:mailutils src:mysql-connector-c++ src:pike7.8 src:pmacct src:poco src:qtbase-opensource-src src:slurm-llnl src:sope src:vtk6 src:zabbix

> Dear Maintainer,

> The mariadb-10.1 packages no longer build the mariadb-test &
> mariadb-test-data packages, but the version in testing still does.
> This prevents britney from migrating the package to testing [0]:

>  trying: mariadb-10.1
>  skipped: mariadb-10.1 (1827, 1009, 24)
>      got: 71+0: a-10:i-32:a-3:a-3:a-3:m-3:m-7:m-3:p-3:s-4
>      * mips64el: mariadb-test

> Because mariadb-10.2 is not going to migrate to testing any time soon,
> the -test* packages need to be built by the mariadb-10.1 package again
> now that its version uses an epoch.

> [0] https://release.debian.org/britney/update_output.txt

Hello Bas,

this reasoning is incorrect or incomplete. Stopping to build binaries
without reverse dependencies is something Debian packages do all the
time. It is in not a bug in the specific package to do so. Our
infrastructure needs to be able to handle this.

See e.g. https://packages.qa.debian.org/d/d-conf.html which dropped a
transitional package in 0.26.1-1 and migrated without error.

I am downgrading this bug because it now blocks the mariadb from
transitioning to testing itself, hiding other possible problems.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'