[debian-mysql] Serious mess while upgrading mysql server

[Didier Kryn]

     Dear mysql Debian maintainers,

     As the administrator of a few Dell PowerEdge servers running Debian 
Wheezy, I made a general upgrade of two machines today. This triggered 
an upgrade of our mysql servers which had several consequences:

     1) the new version (5.5.40) is not fully compatible with version 
5.5.38 . The mysql administrator complained that his service would not 
work without changing configuration files.
     2) the simple fact of restarting a server while it is involved in 
databases replications also causes serious harm according to him.

     Would you be kind enough to consider the following suggestions:

     1) when a new version is not fully compatible with the previous 
one, maybe the two versions might be in the repository, but the new one 
*not* considered an upgrade of the old one, so that routine upgrades do 
not touch it but the administrator must explicitely install one and 
remove the other (like for java-6 vs java-7).

     2) Even for simple upgrades (the ones which do not touch the user 
interface), when about to stop the mysql server, display a warning about 
the possible consequences and ask if the administrator really wants to 
continue.

     Thank you for your attention.

     Didier Kryn
     Laboratoire APC
     Universite Paris-Diderot

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20141104/246c47cd/attachment.html>