Your message dated Mon, 3 Nov 2014 13:36:48 +0100 with message-id <20141103123648.gh8...@betterave.cristau.org> and subject line Re: Bug#767587: please prevent auto-removal of mysql-workbench from "testing" has caused the Debian Bug report #767587, regarding please prevent auto-removal of mysql-workbench from "testing" to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767587: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org 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? Please advise. -- Cheers, Dmitry Smirnov GPG key : 4096R/53968D1B --- It is a fine thing to be honest, but it is also very important to be right. -- Winston Churchillsignature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---On Mon, Nov 3, 2014 at 23:27:42 +1100, Dmitry Smirnov wrote: > Hi Ivo, Julien, > > On Sat, 1 Nov 2014 12:33:51 Ivo De Decker wrote: > > 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. > > I found that mysql-workbench actually do not require mysql client therefore > I've decided to demote "virtual-mysql-client" to Recommends and also (after > discussion with Julien) to add "mysql-client" as first alternative as follows: > > mysql-client | virtual-mysql-client > > The updated mysql-workbench/6.2.3+dfsg-7 is in "unstable" so you may consider > to unblock it if you think it may serve as easier solution to the AUTORM > problem. > mariadb-5.5 is already removed so I don't think the autorm is an issue anymore, but in any case that change is an improvement IMO so I've just unblocked 6.2.3+dfsg-7. Thanks! Cheers, Juliensignature.asc
Description: Digital signature
--- End Message ---