Christian: There are too many things that could go wrong for users if the server itself ignores something in the config file and uses what it considers a safe default.
For the packaging we are working on working around the issue of the server not starting in cases where users have disabled the automatic starting/stopping of services, and this could potentially be extended to include cases where the config contains invalid options (i.e. print a warning and don't try to run mysql_upgrade instead of throwing an error). But this might not cover all the use cases you mention, since some of those packages might be expecting the server to be up and running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571865 Title: mysql fails to start after upgrade if previous defaults were customised To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1571865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
