Bug#921488: [debian-mysql] Bug#921488: libmariadb3: OpenSSL license contamination of GPL reverse-dependencies

2019-02-05 Thread Steve Langasek
On Wed, Feb 06, 2019 at 07:21:46AM +0200, Otto Kekäläinen wrote:
> The OpenSSL licence will change from 3.0.0 onwards
> (https://www.openssl.org/source/license.html) but you are right that
> for version 1.1.1 the SSLeay clause applies. MySQL and MariaDB has the
> OpenSSL exception, and YaSSL has been used due to earlier
> interpretation by non-maintainers that it might be needed, but
> currently I think using OpenSSL is the right thing to use, just like
> upstream MariaDB uses as well.

How does your statement that you think it is "the right thing to use" help
the maintainers of the various packages in the archive that are not
violating the GPL?  What action do you expect them to take for the buster
release?

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature


Bug#921488: [debian-mysql] Bug#921488: libmariadb3: OpenSSL license contamination of GPL reverse-dependencies

2019-02-05 Thread Otto Kekäläinen
Hello!

The OpenSSL licence will change from 3.0.0 onwards
(https://www.openssl.org/source/license.html) but you are right that
for version 1.1.1 the SSLeay clause applies. MySQL and MariaDB has the
OpenSSL exception, and YaSSL has been used due to earlier
interpretation by non-maintainers that it might be needed, but
currently I think using OpenSSL is the right thing to use, just like
upstream MariaDB uses as well.