> The mysql->mariadb switch comes with the unfortunate cost of excluding a > few packages from stretch that require oracle's mysql. > > > Do we need the tech-ctte to get this settled? > > Good luck overriding the security team.
It's not about overriding the security team, it's simply about the MySQL maintainers fixing #848616 [1] or providing reasonable amount of information on how to migrate packages. Their claim that mariadb can simply be used as a drop-in replacement does not hold true, and I am not the only package maintainer stumbling over that. This package does not require Oracle's MySQL, it requires a root user that can authenticate to the database and use it in its entirety, a feature which was deliberately broken in mariadb. Unfortunately, the MySQL maintainers do not see an issue with that and ignore threads about it on their mailing list. So, whether a drop-in replacement in a transition should break a basic API for everyone clearly is something for the tech-ctte to decide. I am not talking about removing Oracle's MySQL. -nik [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848616 -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Hundeshagenstr. 26 · 53225 Bonn Mobile: +49-1520-1981389 · https://www.dominik-george.de/ Teckids e.V. · FrOSCon e.V. Fellowship of the FSFE · Piratenpartei Deutschland Opencaching Deutschland e.V. · Debian Maintainer LPIC-3 Linux Enterprise Professional (Security)
signature.asc
Description: PGP signature
_______________________________________________ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
