Debian DPL Threatens to Leave SPI Over Sun Java
An anonymous reader writes "A three-week-long flame war in debian-devel over the new Java Distribution License has culminated in Anthony Towns, the newly elected Debian Project Lead, offering to separate Debian from its legal representative, SPI. This came as a response to SPI member John Goerzen's objections to the Debian project's interaction with Sun's legal team around the new JDL license without review from SPI's lawyers."
These are the problems:3 70245
3 70295
3 70296
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
The US places export restrictions on certain types of software (mostly encryption related stuff), which Sun has reflected in it's license. Since Debian can't/won't control which country has access to US-based mirrors then that means that they can't fuffill the obligation to screen out illegal downloads from certain countries and such. According to this license the work around Debian has used in the past is to have non-US for exported restricted software. Which is basicly you can only have the software on non-US based mirrors.
Debian has gotten rid of non-US for Sarge due to the relaxation of export controls by the U.S. government. But it would still violate Sun's licensing.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
This is Sun's obnoxiousness showing with this one:
""" (c) you do not combine, configure or distribute the Software to
run in conjunction with any additional software that implements
the same or similar functionality or APIs as the Software;"""
The bug author mentions the Java version of Python, but basicly it would make things like a distro shipping GCJ and Sun's java would be a licensing violation.
Obviously (in My eyes) Sun chooses this for two reasons:
A. To keep it's java runtime pure and functional. Avoids bug-inducing conflicts.
B. Help kill off Free software java implimentation.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
In Sun's License states that you can't modify any sort of copyright notices and whatnot. But by splitting the package up like Debian does they can't avoid modifying this stuff. Thusly Debian is violating Sun's distribution license.
Debian can ship non-free stuff in non-free obviously according to their bylaws.. but Debian doesn't have the authority to break OTHER people's licenses.
Sun says that this is OK and it's legal mumbo jumbo they can ignore. Debian's lawyer are basicly saying we can't violate Sun's licenses... ESPECIALLY without a discussion and you should pull the package from non-free until Sun fixes it's licensing so that Debian can use it legally.
This has happenned before with other software. Sun's license is shit and should be avoided by any sort of sane Linux distribution.
None of that happened this time. There may be good reasons for that, but stating that this case was handed just like any other sounds like a lie to me... but, like I said I'm not an expert, please enlighten me.