Hi,
obviously, you raised the severity of the bug mentioned below to serious
without providing any justification.
I am still waiting for…
…some official decision that this huge change will be made during the freeze
without a transition,
…the MySQL/MariaDB maintainers to fix their packages.
Concerning the latter, both upstream mariadb and the maintainers here claim
that mariadb is a drop-in replacement for mysql, but it turns out it isn't as
they decided to change the default behaviour in a very incompatible way.
The maintainers do not appear to be able to advise others on the unadvertised
breakage they created by crippling the UNIX socket in mariadb by default.
Right now, dropping MySQL support everywhere seems to be the only viable
solution.
Do we need the tech-ctte to get this settled?
Cheers,
Nik
-------- Ursprüngliche Nachricht --------
Von: Debian testing autoremoval watch <nore...@release.debian.org>
Gesendet: 12. Januar 2017 05:39:08 MEZ
An: osmalch...@packages.debian.org
Betreff: osmalchemy is marked for autoremoval from testing
osmalchemy 0.1.+2-2 is marked for autoremoval from testing on 2017-02-10
It (build-)depends on packages with these RC bugs:
848287: python-testing.mysqld: (build-)depends on mysql-{client,server}
_______________________________________________
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
