> If it has the old usr.sbin.mysqld (and an uninstalled dist file) you
have hit the "bug"
By "uninstalled dist file", do you mean usr.sbin.mysqld.dpkg-dist? I
expect your scenario to occur if the user previously modifies the
apparmor profile. In this case, on upgrade, the user should be prompted
to merge customisations manually and asked whether to use the old or new
file. In the case of a non-interactive upgrade, the old file will be
used, and the new one left renamed so that the user can fix it later
manually.
If the old file is used, then you will hit the issue you've described,
but this isn't a bug because Debian policy says that old customised
configurations must not be blindly clobbered and we have no finer-
grained way to bring forward those customisations.
Your report said (automatically generated by apport):
modified.conffile..etc.apparmor.d.usr.sbin.mysqld: [modified]
mtime.conffile..etc.apparmor.d.usr.sbin.mysqld: 2013-08-18T11:48:56.903852
So I think this is exactly what happened to you when you or some script
changed the old apparmor profile back on 18 August 2013. So I'll mark
this bug Invalid on that basis.
** Changed in: mysql-5.6 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455773
Title:
mysql will not start after 5.5 to 5.6 upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1455773/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
