https://bugzilla.redhat.com/show_bug.cgi?id=1862616 Jerry James <loganjerry@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Jerry James <loganjerry@xxxxxxxxx> --- (In reply to Qiyu Yan from comment #1) > We have > - https://github.com/videlec/e-antic/blob/master/COPYING : GPLv3+ > (with "or later version claim") > - https://github.com/videlec/e-antic/blob/master/COPYING.LESSER : LGPLv3 > (without that claim) > in this case, should we continue use a LGPLv3+, or mark it as GPLv3+ or > LGPLv3, I am totally new to dealing with Licenses and don't know what to do > in this case. Yes, the license situation is kind of confusing. Here is my understanding of it. - The actual text in COPYING and COPYING.LESSER does not matter (sort of). What matters is the text in the actual source files. - Some of the source files refer to LGPLv2+. For example, see poly_extra/has_real_root.c. - Some of the source files refer to LGPLv3+. For example, see renf_elem/clear.c. - Some of the source files refer to the FLINT license, which they claim is GPLv2+. For example, see e-antic/nf.h. - FLINT has clarified that its license is LGPLv2+, not GPLv2+. The latest release, which we have in Rawhide, has the updated license. The upstream for both FLINT and antic, wbhart, has clarified this in an issue where a user is confused about the antic license: https://github.com/wbhart/antic/issues/43. - The upstream for e-antic referred to the antic clarification when asked about the e-antic license: https://github.com/videlec/e-antic/issues/100. That is the URL in the comment just above the License tag in e-antic.spec. >From this, I conclude that all of the source files are licensed LGPLv2+, LGPLv3+, or with the FLINT license, which is LGPLv2+. The only way to combine LGPLv2+ and LGPLv3+ is to arrive at LGPLv3+, which is what I put in the License field. Whew! > I may take this not so quick due to setting up buildroot is so slow, > tomorrow I will try it under a proxy. Sure, no rush. Thank you for looking at this. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
