Skip to content
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

Missing required license text for GPL-2.0-with-OpenSSL-exception in cryptsetup #281

Open
farislam opened this issue Aug 31, 2021 · 3 comments

Comments

@farislam
Copy link

Hello All,
We are facing issue with GPL-2.0-with-OpenSSL-exception in cryptsetup. We need a valid license for it.

@goneall
Copy link
Member

goneall commented Aug 31, 2021

@farislam Can you be a bit more specific on the issue? If there needs to be a new SPDX listed license or a new SPDX listed license exception, you can submit a request. See the new license request documentation for information.

You can also create a LicenseRef within the SPDX document with the complete text of the license. See the Other Licensing Information chapter in the spec for details.

@farislam
Copy link
Author

farislam commented Sep 1, 2021

We are using this tool spdx-tools-2.2.5-jar-with-dependencies.jar to verify our spdx Document. Then we get this error:
invalid: Missing required license text for GPL-2.0-with-OpenSSL-exception in cryptsetup. GPL-2.0-with-OpenSSL-exception license is not present in SPDX license list. So what do you suggest here? Should we raise a request or create a LicenseRef within the SPDX document with the complete text of the license?

@goneall
Copy link
Member

goneall commented Sep 1, 2021

Should we raise a request or create a LicenseRef within the SPDX document with the complete text of the license?

Since it takes some time to get a license on the license list (minimum 2 months), I suggest creating a LicenseRef and adding the text to the LicenseRef.

BTW - There is a newer version of the SPDX tools available you might want to try - https://github.com/spdx/tools-java

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants