You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We received a SciPy bug report about colamd.c in the vendored SuperLU code claiming that the code is under the LGPL license: scipy/scipy#21234. The problematic mention is at:
terms of the GNU LGPL, provided that the Copyright, this License,
The code isn't actually LGPL-licensed; the BSD license mention at the top of the same file is correct, as discussed in more detail in the linked SciPy issue. The LGPL mention is still problematic, since there are now two conflicting licenses mentioned in the same file, and the LGPL mention is going to trigger extra work for Linux distro packagers and anyone else who uses license checkers to carefully analyze code for license compliance.
This problem was introduced in commit 44f2c5e. The right fix I believe is to remove the offending bit of code comment that contains "LGPL". I'd be happy to open a PR for that if that helps.
The text was updated successfully, but these errors were encountered:
We received a SciPy bug report about
colamd.c
in the vendored SuperLU code claiming that the code is under the LGPL license: scipy/scipy#21234. The problematic mention is at:superlu/SRC/colamd.c
Line 84 in 6f7ea89
The code isn't actually LGPL-licensed; the BSD license mention at the top of the same file is correct, as discussed in more detail in the linked SciPy issue. The LGPL mention is still problematic, since there are now two conflicting licenses mentioned in the same file, and the LGPL mention is going to trigger extra work for Linux distro packagers and anyone else who uses license checkers to carefully analyze code for license compliance.
This problem was introduced in commit 44f2c5e. The right fix I believe is to remove the offending bit of code comment that contains "LGPL". I'd be happy to open a PR for that if that helps.
The text was updated successfully, but these errors were encountered: