-
Notifications
You must be signed in to change notification settings - Fork 25
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
GNU-All-permissive-Copying-License #93
Comments
@sergiomb2 this is the place. My hunch is that trivy does not use proper SPDX licenses? |
Hi, but I think maybe it misses one package , since in my shell seems I don't have the problem |
cat go-vendor-tools.toml
|
I reproduced the error in ipython
|
So if we unwind the twine ball:
A solution would be to fix trivy and to fix google/licenseclassifier, but this is IMHO a long winding road with not much bright light at the end. Another solution would be to fix go-vendor-tools to use scancode-toolkit instead for a proper and correct license detection. There are many many other things to unpack as the license detection by https://github.com/google/licenseclassifier in https://github.com/moby/buildkit/archive/refs/tags/v0.13.2.tar.gz seems incomplete and incorrect, and the other Go tool https://github.com/google/licensecheck/ which is used otherwise for the official go.pkg.dev is also incorrect/wrong. For instance https://pkg.go.dev/kernel.org/pub/linux/libs/security/libcap/psx is NOT under the GPL but under a choice of BSD-3-Clause OR GPL-2.0-only. If you are packaging for Fedora you must report the license choice and not pick one. (This is the Fedora way) On the side, I noted a few smaller license detection issue in ScanCode and I will file and fix them there. It looks like Go is a somewhat of a mess wrt. to licensing clarity :] |
many thanks for all the info , I will report soon to Fedora golang SIG , yes we are packaging go packages in Fedora |
Thanks for your insight, @pombredanne.
For the record, support for scancode in go-vendor-tools is blocked on aboutcode-org/scancode-toolkit#3720 and/or me rewritting my WIP patch to use the scancode python API instead. In any case, I plan to make the following changes in the go-vendor-tools package:
That license was not determined by trivy. Licenses in go-vendor-tools.toml that @sergiomb2 pasted in are manually specified by the user when the go-vendor-tools license detector cannot find them. Packagers need to ensure that they are inputting the proper license expression when using that feature.
For the most part, it's not terrible, but there's some packages that do atypical things. As for the original issue, would it be possible to add a |
is here where we need fill in the License tag ?
The text was updated successfully, but these errors were encountered: