[Python-modules-team] Bug#848287: Fwd: osmalchemy is marked for autoremoval from testing

2017-01-12 Thread Andreas Beckmann
On 2017-01-12 13:16, Dominik George wrote: > 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. Good, I thought you were questioning the switch in general.

[Python-modules-team] Bug#848287: Fwd: osmalchemy is marked for autoremoval from testing

2017-01-12 Thread Dominik George
> 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

[Python-modules-team] Bug#848287: Fwd: osmalchemy is marked for autoremoval from testing

2017-01-12 Thread Andreas Beckmann
On 2017-01-12 10:10, Dominik George wrote: > Hi, > > obviously, you raised the severity of the bug mentioned below to serious > without providing any justification. You won't stop this transition. The earlier we get mysql-5.6 removed from stretch the better s.t. we can test upgrade paths to

[Python-modules-team] Bug#848287: Fwd: osmalchemy is marked for autoremoval from testing

2017-01-12 Thread Dominik George
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.