Comment 18 for bug 1592669

At my home I keep Mysql usually disabled until I need it, but it may
happen, in a few cases, you might have an another mysql (custom install)
running.
Maybe the installer could open an dialog and asks if the user wants the
service to be started automatically for the upgrade (and then disabled) or
keep it unconfigured.

2017-05-03 1:40 GMT-03:00 Lars Tangvald <email address hidden>:

> On 02. mai 2017 23:49, Larika wrote:
> > If I can suggest, keep it simple.
> >
> > if the service is disable :
> >
> > enable
> > start if stopped
> > upgrade
> > stop if was stopped
> > disable
> >
> > User will find package upgraded but in the same state as he left it.
> >
> > If it's enabled, just check before if the service is loaded and upgrade.
> >
> > I think it's important to give users an updated package, ready to use,
> > as he left it.
> >
> > Thanks for your work!
> >
> Ideally we'd always leave the package _and_ database in a fully upgraded
> state, but I don't think we can/should override the user's service
> settings.
> However, the only situation where we won't be able to upgrade the
> database is if the service is disabled and the server is running; If the
> service is disabled but the server is stopped, we'll start the server in
> a manual way (in general we will no longer use the service system during
> postinst) and run mysql_upgrade.
>
> --
> Lars.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1658034).
> https://bugs.launchpad.net/bugs/1592669
>
> Title:
> postinst fails when daemon is not running (or is disabled by policy-
> rc.d)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/
> 1592669/+subscriptions
>