Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#37437 - [lz4] incorrect license and missing library
Attached to Project:
Community Packages
Opened by Jed Brown (jedbrown) - Monday, 21 October 2013, 17:55 GMT
Last edited by Sébastien Luttringer (seblu) - Wednesday, 23 October 2013, 18:46 GMT
Opened by Jed Brown (jedbrown) - Monday, 21 October 2013, 17:55 GMT
Last edited by Sébastien Luttringer (seblu) - Wednesday, 23 October 2013, 18:46 GMT
|
DetailsDescription:
The lz4 package metadata claims a BSD license, but this only applies to the LZ4 library, not the command-line tool, which is GPLv2. Meanwhile, the lz4 library and header is not installed, though I think it would be useful. Additional info: * lz4-106-1 * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Wednesday, 23 October 2013, 18:46 GMT
Reason for closing: Fixed
Additional comments about closing: Both licenses referenced in license field.
Wednesday, 23 October 2013, 18:46 GMT
Reason for closing: Fixed
Additional comments about closing: Both licenses referenced in license field.
COPYING file in trunk root: GPL ; https://code.google.com/p/lz4/source/browse/trunk/COPYING
CLI C file: GPL ; https://code.google.com/p/lz4/source/browse/trunk/lz4cli.c
What they call at some place library: BSD ; https://code.google.com/p/lz4/source/browse/trunk/lz4.c
So I will add GPL into the license field.