Hi Lisandro, [I am the new maintainer of dbconfig-common, sorry that it took so long to get to this bug.]
On Tue, 30 Apr 2013 22:59:43 -0300 Lisandro Damián Nicanor Pérez Meyer <lisan...@debian.org> wrote: > Hi! I've just upgraded tt-rss and it happened to also upgrade mysql. tt-rss > tried to reconfigure the database (I still don't know why, because it tries to > create tables that are already there) but mysql was stopped because of the > upgrade. > > I needed to log in a second shell and start mysql to let the process finish > :-/ Let's discuss what the best behavior would be if dbconfig-common would check if the database server is running, but it turns out it is not. The most reasonable thing I can think of is tell the admin that server is not running and then? Abort? Ignore? Although the message could be improved in this case, I think that you would still get the same options (and thus behavior) as now. Do you agree or do you see this different (than please explain). If you agree, I think this bug should be wishlist severity as the message might be dedicated for this issue. However, trivially it would add more complexity to the logic, which is already horrible to oversee (lot's of possible paths). Paul
signature.asc
Description: OpenPGP digital signature
