I think I know the reason and a way to reproduce this. I have ran into same issue today when I have installed mariadb on sid, then I have added official mariadb repo and I have run upgrade. Hopefully this was fresh install with no DB, so I just have purged it.
Пт, 3 лип. 2015 о 16:45 Otto Kekäläinen <o...@seravo.fi> пише: > 2015-07-03 1:14 GMT+03:00 Otto Kekäläinen <o...@seravo.fi>: > > Basically what you Yuril did was removed all configuration and data > > files, and then installed. For some reason the mysqld daemon did not > > start on your system, and the failure became visible during an upgrade > > where the system restarts the service. > > I've tested running the upgrade with different scenarios and everything > works. > > Basically, if you ever get into such a situation again, please try to > debug the exact reason why mysqld refuses to start. Best tip is to > look at the /var/log/mysql/error.log > > You can always purge your installation along with any configs and > original binary data, and then import a database dump into a fresh > installation, but that is not recommended. Surely it should be > possible to pinpoint why mysqld does not start (and thus why dpkg > hangs at the service restart step). >
