[debian-mysql] Bug#852267: upgrading mariadb-server-10.0 to mariadb-server-10.1 removed it instead of upgrading

[Jean-Marc]

Wed, 1 Feb 2017 00:18:18 +0200
Otto Kekäläinen <otto at debian.org> écrivait :

> Thank you very much Jean-Marc for helping with testing!

I helped with great pleasure.

> 
> Can you please also try running apt-get purge mysql-* and see if it removes
> the remnants cleanly? But not too cleanly, mysqld binary or /var/lib/mysql
> used by mariadb-10.1 should not get deleted by the mysql purge (one user
> reported he suffered such a case).

So, after the dist-upgrade + autoremove --purge, I listed remaining packages containing mysql:
$ dpkg --list | grep mysql
ii  default-mysql-client            1.0.2                       all          MySQL database client binaries (metapackage)
ii  default-mysql-server            1.0.2                       all          MySQL database server binaries and system database setup (metapackage)
ii  libdbd-mysql-perl               4.041-1                     amd64        Perl5 database interface to the MariaDB/MySQL database
ii  mysql-common                    5.8+1.0.2                   all          MySQL database common files, e.g. /etc/mysql/my.cnf
rc  mysql-server-5.5                5.5.54-0+deb8u1             amd64        MySQL database server binaries and system database setup

So, mysql-common 5.8+1.0.2 is still installed and mysql-server-5.5 is removed but Config files remain on the machine.

And I simulated the purge you described:
$ apt-get purge --simulate mysql-*
[...]
The following packages were automatically installed and are no longer required:
  galera-3 libaio1 libdbi-perl libjemalloc1 libreadline5 libterm-readkey-perl rsync socat
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  default-mysql-client* default-mysql-server* libdbd-mysql-perl* libmariadbclient18* mariadb-client-10.1* mariadb-client-core-10.1* mariadb-common*
  mariadb-server-10.1* mariadb-server-core-10.1* mysql-common* mysql-server-5.5*
0 upgraded, 0 newly installed, 11 to remove and 0 not upgraded.
Purg default-mysql-client [1.0.2]
Purg default-mysql-server [1.0.2]
Purg libdbd-mysql-perl [4.041-1]
Purg libmariadbclient18 [10.1.21-5]
Purg mariadb-server-10.1 [10.1.21-5]
Purg mariadb-client-10.1 [10.1.21-5]
Purg mariadb-client-core-10.1 [10.1.21-5]
Purg mariadb-server-core-10.1 [10.1.21-5]
Purg mariadb-common [10.1.21-5]
Purg mysql-common [5.8+1.0.2]
Purg mysql-server-5.5

Apparently, it is too cleanly.

:-)

I think it comes from the dependency between mysql-common and mariadb:
$ apt rdepends mysql-common 
mysql-common
Reverse Depends:
  PreDepends: mysql-server-5.5 (>= 5.5.54-0+deb8u1)
  Depends: mariadb-common (>= 5.6.25)
  Depends: libmariadbclient18

So, I think you can purge mysql-server-5.5 without any problem but not mysql-common:
$ apt purge --simulate mysql-server-5.5
[...]
The following packages will be REMOVED:
  mysql-server-5.5*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Purg mysql-server-5.5


For your info, there is the files from mysql-server-5.5 remain on my VM:
$ dpkg --listfiles mysql-server-5.5
/etc
/etc/logrotate.d
/etc/logcheck
/etc/logcheck/ignore.d.paranoid
/etc/logcheck/ignore.d.paranoid/mysql-server-5_5
/etc/logcheck/ignore.d.server
/etc/logcheck/ignore.d.server/mysql-server-5_5
/etc/logcheck/ignore.d.workstation
/etc/logcheck/ignore.d.workstation/mysql-server-5_5
/etc/init.d
/etc/apparmor.d
/etc/mysql
/etc/mysql/conf.d
/etc/mysql/conf.d/mysqld_safe_syslog.cnf

I checked the /var/log/apt/history.log and mysql-server-5.5 was removed during the dist-upgrade.

And this process does not purge config files.

I do not know if it is really usefull to keep them.

Regards,

Jean-Marc <jean-marc at 6jf.be>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20170201/4422d826/attachment.sig>