Hi Dan, On 28-10-15 11:38, 積丹尼 Dan Jacobson wrote: > The problem is probably at the phpmyadmin upgrade script level, not the > debconf or whatever deep levels under the hood. Can't it e.g., check if > mysql is running, and then abort very early so that nothing is tinkered > with that will need sewing up?
Yes it can check, but that doesn't help, as the upgrade process already started before ANY question or script by the package runs (all the required files are already unpacked on the system). Either the mysql server is running and everything is fine, or it isn't running and then what? Maybe the mysql database is not on the localhost (so it would need logic to detect that; can be done). Or it is not provided by mysql, but by e.g. MariaDB (I am not sure if that matters, so never mind). Now, let's assume that it detect all that stuff properly and now knows for sure that the database is not running but that it NEEDS to connect to the server to upgrade properly, because the database needs to match the already unpacked files on the system. It would need to raise the issue to error level to get the proper attention and that is exactly what dbconfig-common is already doing. Including providing you with all the options that I can think of to handle the situation: abort (such that you can easily retry once you fixed the underlying issue), ignore (such that the upgrade appears successful but you have to handle the situation manually outside of the upgrade tools view if you want your package to work properly), retry now during the upgrade (which allows you to start your server in the mean time such that the retry actually can succeed). What else do you desire? Paul
signature.asc
Description: OpenPGP digital signature
