[debian-mysql] vivid related testing

[Otto Kekäläinen]

Hello!

Using the two PPA's we have for mysql-5.6 test packages and
mariadb-10.0 test packages I've simulated multiple installation and
upgrade scenarios. I decided to document my testing by sending this
message to the list.

[x] clean trusty virtual machine, both PPA's enabled, and installed
mariadb-server -> OK, with /etc/alternatives/my.cnf in place correctly

[x] mariadb-5.5 on a trusty machine, both PPA's enabled, and ran
upgrade ->  /etc/alternatives/my.cnf in place correctly but
mariadb-server didn't get updated

$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  mariadb-server mysql-common
The following packages will be upgraded:
  libmysqlclient18 mariadb-common

[x] mariadb-5.5 on a trusty machine, both PPA's enabled, and ran
dist-upgrade ->   /etc/alternatives/my.cnf in place correctly but
mariadb-server-5.5 got stopped and removed

$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libaio1 libdbd-mysql-perl libdbi-perl libmariadbclient18 libmysqlclient18
  libterm-readkey-perl mariadb-client-core-5.5 mariadb-common
  mariadb-server-core-5.5 mysql-common
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  mariadb-client-5.5 mariadb-server mariadb-server-5.5
The following packages will be upgraded:
  libmysqlclient18 mariadb-common mysql-common


[x] mariadb-5.5 on trusty machine, both PPA's enabled, and installed
mariadb-server (not upgrade, thus mysql-common didn't upgrade) -> OK,
but with fallback my.cnf -> mariadb.cnf link

[x] mariadb-10.0 installed with old mysql-common, installed
mysql-common so that it installed the alternatives system on top of
fallback symlink -> OK, my.cnf.migrated continues to operate mariadb
correctly (output with details below)


Preparing to unpack .../mysql-common_5.6.24-0ubuntu1~ppa1~14.04.1_all.deb ...
Moving obsolete conffile /etc/mysql/conf.d/.keepme out of the way...
Obsolete conffile /etc/mysql/my.cnf has been modified by you.
Saving as /etc/mysql/my.cnf.dpkg-bak ...
Unpacking mysql-common (5.6.24-0ubuntu1~ppa1~14.04.1) over
(5.5.41-0ubuntu0.14.04.1) ...
Tehdään asetuksia: mysql-common (5.6.24-0ubuntu1~ppa1~14.04.1) ...
update-alternatives: using /etc/mysql/my.cnf.fallback to provide
/etc/mysql/my.cnf (my.cnf) in auto mode
Removing obsolete conffile /etc/mysql/conf.d/.keepme ...
Moving /etc/mysql/my.cnf.dpkg-bak to /etc/mysql/my.cnf.migrated
Using your previous configuration through /etc/mysql/my.cnf.migrated
update-alternatives: using /etc/mysql/my.cnf.migrated to provide
/etc/mysql/my.cnf (my.cnf) in auto mode
timo at timo-virtual-machine:/var/log$ ls -la /etc/mysql/
yhteensä 48
drwxr-xr-x   4 root root  4096 huhti 19 21:23 .
drwxr-xr-x 134 root root 12288 huhti 19 15:16 ..
drwxr-xr-x   2 root root  4096 huhti 19 21:23 conf.d
-rw-------   1 root root   277 huhti 19 20:18 debian.cnf
-rwxr-xr-x   1 root root  1312 huhti 14 16:50 debian-start
-rw-r--r--   1 root root   744 huhti 14 16:50 mariadb.cnf
drwxr-xr-x   2 root root  4096 huhti 19 20:17 mariadb.conf.d
lrwxrwxrwx   1 root root    24 huhti 19 21:23 my.cnf -> /etc/alternatives/my.cnf
-rw-r--r--   1 root root   839 helmi 11 17:10 my.cnf.fallback
-rw-r--r--   1 root root  1315 huhti 19 21:23 my.cnf.migrated
-rw-r--r--   1 root root  3505 helmi 19  2014 my.cnf.old
timo at timo-virtual-machine:/var/log$ ls -la /etc/alternatives/my.cnf
lrwxrwxrwx 1 root root 26 huhti 19 21:23 /etc/alternatives/my.cnf ->
/etc/mysql/my.cnf.migrated
timo at timo-virtual-machine:/var/log$ tail /etc/mysql/my.cnf.migrated
#
# If the same option is defined multiple times, the last one will apply.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.

# Import all .cnf files from configuration directory
!includedir /etc/mysql/conf.d/
!includedir /etc/mysql/mariadb.conf.d/



[x] mysql-5.5 on a trusty machine, both PPA's enabled, and ran upgrade
->  same as with mariadb

$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  mysql-common mysql-server
The following packages will be upgraded:
  libmysqlclient18


[x] mysql-5.5 on a trusty machine, both PPA's enabled, and ran
dist-upgrade ->  same as with mariadb

$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libaio1 libdbd-mysql-perl libdbi-perl libmysqlclient18 libterm-readkey-perl
  mysql-client-core-5.5 mysql-common mysql-server-core-5.5
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  mysql-client-5.5 mysql-server mysql-server-5.5
The following packages will be upgraded:
  libmysqlclient18 mysql-common


[x] mysql-5.5 on trusty machine, both PPA's enabled, and installed
mysql-server (triggers upgrade correctly) -> OK, with
/etc/alternatives/my.cnf in place correctly (although the install
phase asked for a new password, did it reset the user table?)


[x] mysql-5.6 on trusty machine, both PPA's enabled, and installed
mariadb-server -> OK, with /etc/alternatives/my.cnf updating correctly