Bug#792080: mysql-common: needs to handle upgrades from mariadb-common that creates my.cnf - mariadb.cnf symlink

2015-07-22 Thread Andreas Beckmann
On 2015-07-22 12:54, Robie Basak wrote: move innochecksum manpage to mysql-server-core-5.6, too Please note that these may need to be coordinated with mariadb and percona packaging. mariadb should be fine and src:percona-xtradb-cluster-5.5 was RMed last week. I see No directory,

Bug#792080: mysql-common: needs to handle upgrades from mariadb-common that creates my.cnf - mariadb.cnf symlink

2015-07-22 Thread Andreas Beckmann
On 2015-07-17 13:23, Robie Basak wrote: On Fri, Jul 17, 2015 at 01:10:35PM +0200, Andreas Beckmann wrote: I pushed another one to deregister the my.cnf.fallback alternative on removal, otherwise purge gets noisy about the dangling link. Having looked at your previous patches I feel that you

Bug#792080: mysql-common: needs to handle upgrades from mariadb-common that creates my.cnf - mariadb.cnf symlink

2015-07-22 Thread Robie Basak
Hi Andreas, As always, thank you for looking into this! On Wed, Jul 22, 2015 at 12:48:49PM +0200, Andreas Beckmann wrote: move innochecksum manpage to mysql-server-core-5.6, too Please note that these may need to be coordinated with mariadb and percona packaging. Otherwise we could end

Bug#792080: mysql-common: needs to handle upgrades from mariadb-common that creates my.cnf - mariadb.cnf symlink

2015-07-22 Thread Otto Kekäläinen
2015-07-22 13:54 GMT+03:00 Robie Basak robie.ba...@ubuntu.com: Hi Andreas, As always, thank you for looking into this! On Wed, Jul 22, 2015 at 12:48:49PM +0200, Andreas Beckmann wrote: move innochecksum manpage to mysql-server-core-5.6, too Please note that these may need to be

Bug#792080: mysql-common: needs to handle upgrades from mariadb-common that creates my.cnf - mariadb.cnf symlink

2015-07-17 Thread Andreas Beckmann
On 2015-07-14 18:33, Robie Basak wrote: Hi Andreas, On Sat, Jul 11, 2015 at 03:29:02AM +0200, Andreas Beckmann wrote: Since the issue is hard to describe in detail and with all pitfalls without digging into it and testing it, I rather developed patches that I tested in sid and stretch, to

Bug#792080: mysql-common: needs to handle upgrades from mariadb-common that creates my.cnf - mariadb.cnf symlink

2015-07-17 Thread Robie Basak
Hi Andreas, Some quick answers (without looking at detail): On Fri, Jul 17, 2015 at 01:10:35PM +0200, Andreas Beckmann wrote: I pushed another one to deregister the my.cnf.fallback alternative on removal, otherwise purge gets noisy about the dangling link. Having looked at your previous

Bug#792080: mysql-common: needs to handle upgrades from mariadb-common that creates my.cnf - mariadb.cnf symlink

2015-07-14 Thread Robie Basak
Hi Andreas, On Sat, Jul 11, 2015 at 03:29:02AM +0200, Andreas Beckmann wrote: Since the issue is hard to describe in detail and with all pitfalls without digging into it and testing it, I rather developed patches that I tested in sid and stretch, to ensure sane upgrade paths. The commit

Bug#792080: mysql-common: needs to handle upgrades from mariadb-common that creates my.cnf - mariadb.cnf symlink

2015-07-10 Thread Andreas Beckmann
Package: mysql-common Version: 5.6.25-2 Severity: serious Tags: patch mariadb-common introduced some fallback mode to create a my.cnf - mariadb.cnf symlink (and renames the original my.cnf to my.cnf.old) in case the update-links script is not available. This needs to be handled in mysql-common,