[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ruby2.2: Contains file released under a nonfree license



On Sun, 13 Mar 2016 17:18:12 +0100 Christian Hofstaedtler wrote:

> Francesco,

Hello Christian!

> 
> Thank you for caring about this issue.

You're welcome.

> 
> I'd welcome your help in the upstream bug at
> https://bugs.ruby-lang.org/issues/11844

I cannot directly comment on the upstream issue tracking system, but I
can add my comments here: feel free to forward them upstream or to
point upstream to the Debian BTS bug log.

Upstream seems to claim that there's no problem, since they are in
compliance with the old (troublesome) Unicode license.
It's possible that they comply with the license terms, but that's
not the point.

The point is that the old Unicode license makes those files non-free
and that those files are included (in verbatim or modified form) in the
Ruby interpreter reference implementation!
Hence, Ruby v2.2 (or v2.3) incorporates non-free parts!

In detail, enc/trans files carry a license notice that:

 (a) only grants right to make copy for "internal distribution", thus
     possibly failing DFSG#2

 (b) only grants right to use the information supplied "in the creation
     of products supporting Unicode", thus failing DFSG#6

 (c) does not grant any permission to modify the file, thus failing
     DFSG#3

In case upstream are not familiar with the Debian Free Software
Guidelines (DFSG), the following URL should be mentioned:
https://www.debian.org/social_contract#guidelines

As far as generator.c is concerned, its license notice also has
issues (b) and (c) explained above.

I hope the problematic files may be replaced by more recent versions
released under the current Unicode license:
http://www.unicode.org/copyright.html#Exhibit1

> 
> A text patch explaining the current state for the d/copyright file
> in ruby2.3 would also be very welcome.

This will depend on whether we may or may not consider the old Unicode
files as de-facto re-licensed under the current Unicode license...

Please try to at least investigate this (perhaps by getting in touch
with Unicode, Inc. and asking for clarification).


I hope this helps.
Bye and thanks for pushing in the right direction!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE

Attachment: pgpqr0yfcB6zs.pgp
Description: PGP signature


Reply to: