Bug#852456: RM: mysql-5.6/5.6.30-1

[Andreas Beckmann <anbe@debian.org>]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian.org@packages.debian.org
Usertags: rm

We are nearly ready to get rid of mysql-5.6 in stretch:

Checking reverse dependencies...
# Broken Depends:
net-snmp: snmptrapd
  age 7/10

percona-xtrabackup: percona-xtrabackup-test
  autorm 2017-01-26, unfixed CVE

python-testing.mysqld: python-testing.mysqld
                       python3-testing.mysqld
  *** UNFIXED *** autorm 2017-02-19

ruby-dataobjects-mysql: ruby-dataobjects-mysql
  age 4/5

# Broken Build-Depends:
captagent: libmysqlclient-dev
  age 6/10

cfengine3: libmysqlclient-dev
  age 3/10

embassy-phylip/non-free: libmysqlclient-dev
  age 9/10

net-snmp: libmysqld-dev
  age 7/10

python-testing.mysqld: mysql-client
                       mysql-server
  *** UNFIXED *** autorm 2017-02-19

ruby-dataobjects-mysql: libmysqlclient-dev
                        mysql-server
  age 4/5

ruby-riddle: mysql-server
  age 6/10

sagan: libmysqlclient-dev
  age 7/10


For python-testing.mysqld (and its rdepends osmalchemy) I'd suggest to
temporarily remove them from testing s.t. mysql-5.6 can go away, but
grant them a free unblock ticket if the package is fixed within 2 (4?)
weeks after removal (or if the package can get back in before the
projected autorm date at removal time).
AFAUI, mariadb-10.1 contains the necessary flexibility to have the
database setup script work in a way compatible with mysql, so nothing
from the mariadb side is blocking #848287 from being fixed.


Andreas