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

[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 messages should explain all the problems involved ...
> if you have more questions, just ask.

Thank you for looking at this! I hadn't quite got round to it since I
ended up focusing on the piuparts logger thing on my last pass over the
MySQL packaging.

> Andreas Beckmann (6):
>       mysql-common.postinst: install my.cnf.fallback alternative after rm_conffile my.cnf
>       mysql-common.preinst: revert mariadb-common my.cnf fallback symlink
>       mysql-common.preinst: recover from unmodfied mariadb.cnf as my.cnf.migrated
>       mysql-common.postrm: delete my.cnf.{migrated,old} on purge
>       mysql-common.postrm: only remove alternatives created by our postinst
>       mysql-common: add Breaks: mariadb-common (<< 10.0.20-3~)

These all look fine to me, but I presume depend on mariadb uploading a
10.0.20-3 with corresponding changes? I'm happy to commit this to git
and get an upload (I'm DM now but I don't think I'm in the keyring yet)
but I guess we should coordinate with Otto for a corresponding mariadb
upload?

Robie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20150714/4f87865b/attachment.sig>