2015-06-11 21:56 GMT+03:00 Andreas Beckmann <a...@debian.org>: >> This my.cnf modification was introduced in commit >> https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=90b6bde63c8128eb7f54f16dfeec88081e4bdb0d > > That is, sorry, so utterly wrong ... > Renaming the old my.cnf must be done by mysql-common (using > dpkg-maintscript-helper mv_conffile), because that is the only way to > make dpkg forget about the old conffile (and its hashes) that will be > replaced by a symlink which is (probably) managed by scripts and not by > dpkg. > >> It as absolutely necessary to do, otherwise the package is broken. > > Depends: mysql-common (>= FIXED_VERSION) > > And yes, this config file transition should have started in > mysql-common, not mariadb.
Yes, but I don't have access to upload mysql-common, I can only maintain the mariadb-10.0 package. If I add to mariadb-10.0 "Depends: mysql-common (>= 5.6)" it will stop working for all users in unstable/testing. ..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? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
