[debian-mysql] Bug#767597: Bug#767597: mariadb-server-10.0: piuparts / Package purging left files on system

[Otto Kekäläinen]

Thanks for taking time to file a bug about this. Here is some
additional details i investigated:

- mariadb-server-10.0 (in sid) has piuparts issues in sid:
https://piuparts.debian.org/sid/source/m/mariadb-10.0.html. The file
/etc/mysql/debian.cnf and files in /var/lib/mysql/* are not owned.
- mariadb-server-5.5 (in sid) has no piuparts issues even though it
(AFAIK) has exactly the same layout and installation contents:
https://piuparts.debian.org/sid/source/m/mariadb-5.5.html
- mysql-server-5.5 (in sid) has piuparts issues in sid:
https://piuparts.debian.org/sid/source/m/mysql-5.5.html. The files in
/etc/apparmor.d/local/ are not owned. There is no complaint about
/var/lib/mysql/*.
- mysql-server-5.6 (in experimental) has no piuparts issues, even
though it too (AFAIK) has the same layout and installation contents as
mariadb-server-10.0):
https://piuparts.debian.org/experimental/source/m/mysql-5.6.html

Interestingly the log for mysql-server-5.5 in sid2testing shows these
same /var/lib/mysql/* not owned warnings:
https://piuparts.debian.org/testing2sid/pass/mysql-server-5.5_5.5.39-1.log
- but the run in anyway considered successful by piuparts and there is
a sun icon in the listing at
https://piuparts.debian.org/testing2sid/maintainer/p/pkg-mysql-maint@lists.alioth.debian.org.html
(and by the way, in that screen mariadb-5.5 has two piuparts errors,
and the log says as the faul 'interrupted by the user'). These
/var/lib/mysql/* warning lines can be found elsewhere too (e.g.
https://piuparts.debian.org/jessie/pass/mariadb-server-5.5_5.5.39-2.log)
yet piuparts still say those runs pass.

In the Jessie screen there are no errors for mysql-5.5 or mariadb-5.5:
https://piuparts.debian.org/jessie/maintainer/p/pkg-mysql-maint@lists.alioth.debian.org.html

My MariaDB 5.5 and 10.0 packages are based on MySQL 5.6 packaging in
Debian. It might very well be by design that /var/lib/mysql/* is not
owned by any package, so the important database data don't get purged
accidentally, but I am not sure what is the proper thing to do in the
long run.

Anybody else want to take a shot at this?