Hi Dan, I have the impression you are getting emotional. That is of course all right, but I'll try to keep the talk technical.
On 27-10-15 01:58, 積丹尼 Dan Jacobson wrote: > Can't you guys somehow find a way to ask the patient if he would like > to abort ealier than when you have him already on the operating > table, with his chest open? And then asking him to sew up his chest > by himself? To be honest, we do our bloody best. We do ask if you actually want dbconfig-common to help you in upgrading. You answered yes to that question (or at least had the chance to say no, as the default answer is IMHO correctly set to yes if you used dbconfig-common to install the package in question). Then we check if we can connect to the database and when that fails we allow you to solve the issue in a way that suits your situation, including just ignoring the issue and continue with any upgrade you are doing. I honestly don't think this is asking to "sew up yourself", but maybe you have a suggestion on how to improve the situation. Please remember that your use case is uncommon, but maybe we can better support it. I don't know how though. Just checking for a running mysql isn't going to help. What do you expect dbconfig-common to actually do with that knowledge? The only thing it can properly do is raise an error like dbconfig-common does now and ask the admin how he wishes to handle the situation. Paul
signature.asc
Description: OpenPGP digital signature
