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
RJSONIO licensing effectively non-free by Debian interpretation #2758
Comments
|
For the record, this issue was kindly brought to my attention by a fellow Debian developer, Jonathon Love, when I filed a "request for packaging" of r-cran-rjsonio for Debian: https://bugs.debian.org/802263 |
|
argh, i heard about this. thanks for the report. |
it does support UTF-8 we originally baulked at using it for exactly the same reason, but it actually does. |
|
Looks like the libjson included by RJSONIO is not the problematic one. |
|
btw, thank you jonathon |
|
no worries :) i only know about this because i once tried to package rjsonio for debian, and lintian automagically picked up that a bad license was in the source! |
|
Looking at the code, R_readFromJSON does call into the evil code, but is itself only called from oldFromJSON. The other reference in readJSON.R is protected by if(FALSE). oldFromJSON is only called if a 2nd parameter is given to fromJSON, which we never do. So I think we can rip it out. |
|
Quoting Scott Draves (2015-11-10 17:46:54)
That sounds promising. I can understand if upstream wants to keep backwards compatibility Even so, we can in the Debian packaging of RJSONIO patch the code and
|
|
sounds like this can be handled when rjsonio is packaged, not in beaker's code. |
RJSONIO itself is licensed as BSD-3-Clause but links against libjson which has a license considered non-free by Debian and others: https://wiki.debian.org/qa.debian.org/jsonevil
Please consider switching to either r-cran-rjson or r-cran-jsonlite (i.e. revisit #472).
The text was updated successfully, but these errors were encountered: