[debian-mysql] mysql-5.6 -> unstable

[Clint Byrum]

Excerpts from Robie Basak's message of 2015-06-11 07:22:42 -0700:
> On Wed, Jun 10, 2015 at 02:18:58PM +0000, Bjoern Boschman wrote:
> > can anyone with upload rights pls upload mysql-5.6 to unstable?
> > 
> > https://www.boschman.de/~jesusch/git/mysql/mysql-5.6_5.6.25-1_amd64.changes
> > 
> > changes are commited and pushed to git.
> 
> Please don't, it's broken. Have you actually build tested it?
> 
> I have fixes/reversions in the pipeline. I should have them in git in
> the next few hours.
> 
> However, based on experience from Ubuntu, I wonder if I should fix
> https://launchpad.net/bugs/1447944 before we upload, in order to break
> fewer users?
> 
> In addition to that, any opinion on having a maintainer script disable
> the mysql service somehow if updating between releases and the
> maintainer script can detect that local configuration changes mean that
> mysqld cannot start, rather than failing the maintainer script and thus
> failing the upgrade? It seems to me that this would make for a better
> user experience. We can explain what happened in a critical debconf
> prompt, but at least this way it won't break the user's system (only
> the mysqld service).
> 
> Something like creating /etc/mysql/my.cnf.migrated.disabled in this case
> (when my.cnf was previously modified and thus my.cnf.migrated is
> created) and if that file exists then the service can avoid starting
> mysqld.

I think that's a good plan, and is inline with the policy that services
that cannot be run with the default configuration should not be started.

Not sure if there's any way beyond a Critical debconf message that we
can use to warn them, but anything more we can do would be good.