Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please update Unicode license blurb #277

Open
zeha opened this issue Apr 1, 2016 · 6 comments · May be fixed by #567
Open

Please update Unicode license blurb #277

zeha opened this issue Apr 1, 2016 · 6 comments · May be fixed by #567

Comments

@zeha
Copy link

zeha commented Apr 1, 2016

Please update the unicode license blurb in ext/json/generator/generator.c (under the assumption that the file indeed comes from unicode.org and the new, free, Unicode.org license applies).

See https://bugs.ruby-lang.org/issues/11844 for more discussion/info.

@LukeShu
Copy link

LukeShu commented Jun 24, 2017

This is causing problems for the Parabola GNU/Linux-libre distribution's ruby package. Our current solution is to remove the generator.c file and have it build the pure Ruby version of the gem; which is obviously sub-optimal.

@LukeShu
Copy link

LukeShu commented Jul 5, 2017

The offending code is from the CVTUTF library, which was removed from unicode.org in 2009; perhaps some change to unicode.org/copyright.html affected it, but the license blurb in the file was never changed.

@bill-auger
Copy link

bump

a little love here?

this freedom bug against parabola is nearly four years old and nearly three years old against this repo with no acknowledgement

@bill-auger
Copy link

bump

5 years now - still no acknowledgement?

@voxik
Copy link

voxik commented Jun 2, 2023

This still an issue. This time the UCD license was claimed nonfree and disallowed by Fedora:

https://gitlab.com/fedora/legal/fedora-license-data/-/merge_requests/88

@bill-auger
Copy link

welcome to the party fedrora :)

yeap, this makes 7 years now - yet, not a single acknowledgement from the maintainer - it looks like the only way this will be resolved, is if ruby drops this code-base entirely - unfortunately, the ruby folks were not eager to address it either

@LukeShu LukeShu linked a pull request Feb 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants