Bug#767587: please prevent auto-removal of mysql-workbench from "testing"

[Ivo De Decker <ivodd@debian.org>]

Hi Dmitry,

On Sat, Nov 01, 2014 at 03:27:07AM -0700, Dmitry Smirnov wrote:
> I just got the following notice
> 
> 	mysql-workbench 6.2.3+dfsg-6 is marked for autoremoval from testing on 2014-12-01
> 	
> 	It (build-)depends on packages with these RC bugs:
> 	765664: mariadb-5.5: Multiple security fixes from October 2014 CPU could affect MariaDB
> 
> which makes me worry whether mysql-workbench will be part of Jessie.
> Mysql-workbench depends on "virtual-mysql-client" provided by
> 
>  * mariadb-client-10.0
>  * mariadb-client-5.5
>  * mysql-client-5.5
>  * mysql-client-5.6
>  * percona-xtradb-cluster-client-5.5
> 
> I think it is a bit harsh to remove mysql-workbench from "testing"
> (merely) due to problems in one of the alternatives providing client
> for MySQL connectivity. Besides client package is probably not even
> affected by the security issues...
> 
> What can we do to avoid auto-removal of mysql-workbench from Jessie?

This is a bug in the auto-removal system. I expect mariadb-5.5 to be removed
before 2014-12-01, solving the issue in this case, but if you get the second
notification about this auto-removal, please ping this bug, and I'll prevent
the auto-removal manually.

Cheers,

Ivo