This bug was fixed in the package mysql-5.5 - 5.5.20-0ubuntu1
---
mysql-5.5 (5.5.20-0ubuntu1) precise; urgency=low
* New upstream release.
* d/mysql-server-5.5.mysql.upstart: Fix stop on to make sure mysql is
fully stopped before shutdown commences. (LP: #688541) Also
** Branch linked: lp:ubuntu/mysql-5.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907465
Title:
mysql upstart job must depend on upstart = 0.6.7-2
To manage notifications about this bug go to:
So, if do-release-upgrade -d is used, upstart is in fact upgraded before
mysql, and this problem does not appear. I'm lowering this to Medium,
since that is by far the preffered method.
Unfortunately a much more serious issue turned up, where
/run/mysql/mysqld.sock is not writable due to the
** Branch linked: lp:~clint-fewbar/ubuntu/precise/mysql-5.5/merge-from-
ddebian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/907465
Title:
mysql upstart job must depend on upstart = 0.6.7-2
To