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

[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.

Unfortunately I can't help here ...


Andreas

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

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

[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 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

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

[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 stretch w/o
mysql available.

> 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.

A quick search revealed at least this post to d-d-a from Sep 04, two
months before the first freeze phase:

https://lists.debian.org/msgid-search/1472973251.19451.2.camel@XPS-L322X

> 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.

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.


Andreas

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

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

[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.

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 
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