----- gabs...@lelutin.ca wrote: > Ugh, I fail at reportbug again :( > > real sorry about the initial report. > > here's the real description of the problem: > > > when upgrading from jessie to stretch, the upgrade goes through > without > an error but the end result is that mysql-server-5.5 gets removed and > mysql is not running anymore. > > stretch is supposed to push ppl towards mariadb according to the > (still > work in progress) release notes, however mariadb doesn't get > installed. > > There is no mysql-server, mysql-server-* or mysql-client-* packages > in > stretch so I believe this to be the source of the issue. > > One can fix the problem either by adding default-mysql-server before > upgrading or after. however this poses a problem: > > * before the upgrade, the default-mysql-server package is only > available in jessie-backports > * after the upgrade, you've gotten no notice at all about what's > happening and why the mysql server is not running and not upgraded. > > One way to make this an easier transition would be to have a > mysql-server package in stretch that's a dummy package that depends > on > default-mysql-server, and that has an upgrade notice about the > transition to mariadb that is happening. > > The mysql package names should be reserved for actual mysql packages (default-mysql, virtual-mysql etc. are named so because there isn't a better term for "mysql-ish"). While the current situation with mysql being half-uninstalled is pretty odd, we shouldn't automatically replace mysql-server with mariadb-server, as it can cause problems for users who want to keep using mysql, while those who are fine with either just need to install mariadb after the upgrade.
-- Lars