Hi Dan On 26-10-15 19:53, 積丹尼 Dan Jacobson wrote: > Well that package should not assume all users are running mysql all the > time, and only find out too late in its upgrade procedure, causing > things to get stuck in an non-ideal state, causing much work...
And lots of setups don't need mysql running on the localhost. So
checking for a running mysql doesn't work in lots of cases.
> Instead it should first check, and if it finds mysql not running it
> should say
> "Mysql is not running. Please start it and hit RET, or type "a" to
> abort." etc.
The current checks should cover this. Do you think the error message
should be improved? The current error message is below. Which point is
not clear enough?
_Description: Next step for database upgrade:
An error occurred while upgrading the database:
.
${error}
.
Fortunately, ${dbfile} should hold a backup of the database, made just
before the upgrade (unless the error occurred during backup creation, in
which case no changes will have been applied yet). Your options are:
* abort - Causes the operation to fail; you will need to downgrade,
reinstall, reconfigure this package, or otherwise manually intervene
to continue using it. This will usually also impact your ability to
install other packages until the installation failure is resolved.
* retry - Prompts once more with all the configuration questions
(including ones you may have missed due to the debconf priority
setting) and makes another attempt at performing the operation.
* retry (skip questions) - Immediately attempts the operation again,
skipping all questions. This is normally useful only if you have
solved the underlying problem since the time the error occurred.
* ignore - Continues the operation ignoring dbconfig-common errors.
This will usually leave this package without a functional database.
Paul
signature.asc
Description: OpenPGP digital signature
