On 2015-06-15 11:09, Robie Basak wrote: > On Sun, Jun 14, 2015 at 02:47:00AM +0300, Otto Kekäläinen wrote: >> ..so at the moment the only thing I can do is to revert all mysql-5.6 >> compatibility in MariaDB, which would be a huge waste of everybody's >> time. Can't we make an exception from the policy here as clearly the >> point of the policy is to make the packages as clean as possible, not >> impossible? > > I'm sorry, I had failed to realise that mariadb was affected by my delay > in uploading mysql-5.6 in this way. I am working on an upload of > mysql-5.6 to fix mysql-common.
Good news! > The new mysql-common replaces the /etc/mysql/my.cnf conffile with a > non-conffile maintainer-script-manager symlink (via > update-alternatives). It is in VCS, though I want to fix a separate bug > before I upload to minimise the impact on users of unstable and testing > who will transition from 5.5 to 5.6 as soon as I upload. I'll take a look at this :-) > Maybe this bug can be reassigned to mysql-common, No, the "fixup code" in mariadb has to go away. > or its severity in > mariadb reduced? It doesn't make sense to remove mariadb from testing. ACK. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
