https://bugzilla.redhat.com/show_bug.cgi?id=1321081 --- Comment #6 from Richard Shaw <hobbes1069@xxxxxxxxx> --- (In reply to Mattia Verga from comment #5) > (In reply to Richard Shaw from comment #4) > > (In reply to Mattia Verga from comment #3) > > > - License in spec file is "GPLv3+ and MIT", but some sources are licensed > > > GPLv2+ and LGPLv2+, so the license should be "GPLv2+ and MIT". > > > Also the COPYING file distributed with the program is GPLv2. > > > The dual license should be explained briefly or with a breakdown. > > > > GPLv3 sources can't be downgraded to GPLv2 so I believe my original entry is > > correct. > You may be right, but the license file bundled in sources is a GPLv2+ > license... I've asked help on the legal mailing list on how to proceed if > the bundled license file is wrong. The "+" specifically means "... or later version". Licensing can get quite complicated but in the case of mixed GPL licenses it's much simpler. All the LGPLv2+ and GPLv2+ sources are upgraded to GPLv3 in the resultant binary. If the LGPLv2+ files ended up in a separate library then we would need to list both. > > > - Please add a note to clarify that Source99 is a file added by you > > > (and specify its license - I think you want to release as MIT) > > > > I haven't worried about this in the past as the appdata file itself > > specifies it's license to be CC0-1.0 (same as the example in the Fedora wiki. > We should document where the sources come from, it should be a best practice > to add a comment about that. But it's not mandatory. > > Let's wait the legal mailing list response about the license. If you examine the file I have copyrighted it and attributed an acceptable licence to the metadata. While it's not specifically referenced in the spec file I believe the requirements have been met. -- 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
