Bug #8249 Linking together with OpenSSL forbidden? Debian migration problems
Submitted: 1 Feb 2005 23:49 Modified: 11 Feb 2005 0:55
Reporter: Christian Hammers (Silver Quality Contributor) (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:Licensing Severity:S3 (Non-critical)
Version:4.0 and 4.1 OS:-
Assigned to: Arjen Lentz CPU Architecture:Any

[1 Feb 2005 23:49] Christian Hammers 
Description:
Hello

The Debian project currently links most application against libmysqlclient10 from 3.23
but after the past FLOSS license clarification wants to migrate to libmysqlclient12 [1].
 
Sadly there seems still to be a problem [2] regarding the OpenSSL license which itself
is not GPL compatible [3].

How does MySQL thinks about this? Will you insert the OpenSSL license to the FLOSS Exception? [4]

bye,

-christian- <ch@debian.org>

[1] http://lists.debian.org/debian-devel/2005/01/msg01757.html (proposal)
[2] http://lists.debian.org/debian-devel/2005/01/msg01956.html (problem)
[3] http://www.fsf.org/licenses/license-list.html#GPLIncompatibleLicenses
[3] And don't quote me saying that adding OpenSSL to the FLOSS Exception is enough 
     to solve the problem, I'm not a lawer, just a frustrated Debia maintainer :-))

How to repeat:
-

Suggested fix:
Relicense everything under the LGPL or hire a lawyer :)
[2 Feb 2005 8:31] Arjen Lentz 
Already working on this since a few days, issue was brought up by Adam Conrad (PHP and Apache maintainer) and Steve Langasek (release manager).
[10 Feb 2005 22:06] Arjen Lentz 
OpenSSL license will be added to FLOSS exception.
[11 Feb 2005 0:55] Arjen Lentz 
The following line has been added to the FLOSS license exception:
===
OpenSSL license (with original SSLeay license)    "2003" ("1998")
===
The new version of the FLOSS exception is v0.3, 10 February 2005.

This text will be used in any build starting from now, however the addition also applies to any existing MySQL release.