Bug 2125487
Summary: | license-fedora2spdx should print friendly error when unknow license is passed as argument | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ralf Corsepius <rc040203> |
Component: | license-validate | Assignee: | Miroslav Suchý <msuchy> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 36 | CC: | msuchy |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | license-validate-10-1.fc37 license-validate-10-1.fc36 license-validate-10-1.fc35 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-09-19 00:18:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ralf Corsepius
2022-09-09 07:51:01 UTC
This happens when you use license which is not valid fedora short name (Callaway id). Artistic is incorrect because it should be either 'Artistic clarified' or 'Artistic 2.0'. I agree that the script should produce a more friendly error. (In reply to Miroslav Suchý from comment #1) > This happens when you use license which is not valid fedora short name > (Callaway id). Artistic is incorrect because it should be either 'Artistic > clarified' or 'Artistic 2.0'. I encountered this with perl packages. Probably 1000s of them use 'GPL+ or Artistic' Unfortunately license-fedora2spdx doesn't provide a reasonably translation for them: # license-fedora2spdx 'GPL+ or Artistic' Warning: we do not have SPDX identifier for GPL+ or Artistic GPL+ or Artistic So I tried license-fedora2spdx 'GPL+' Warning: more options how to interpret GPL+. Possible options: ['GPL-1.0-or-later', 'GPL-1.0-or-later'] GPL-1.0-or-later and license-fedora2spdx 'Artistic' which produces this bug. > I agree that the script should produce a more friendly error. Openly said, I think, in its present shape license-fedora2spdx is completely unusable. FEDORA-2022-0f36435e8e has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0f36435e8e FEDORA-2022-72139afbab has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-72139afbab FEDORA-2022-0699371c4d has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0699371c4d FEDORA-2022-0699371c4d has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-0699371c4d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0699371c4d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. (In reply to Ralf Corsepius from comment #2) > I encountered this with perl packages. Probably 1000s of them use 'GPL+ or > Artistic' https://gitlab.com/fedora/legal/fedora-license-data/-/blob/main/data/GPL-1.0-or-later_OR_Artistic-1.0-Perl.toml > # license-fedora2spdx 'GPL+ or Artistic' This is the right use. It takes it as one license. > license-fedora2spdx 'GPL+' > license-fedora2spdx 'Artistic' This is not. This takes it as two separate licenses, where the second does not exist. We still did not set a good release process for fedora-license-data. And the cadence of data changes there is too fast now. Please take a bit of patience. It will settle down in the upcoming weeks. FEDORA-2022-72139afbab has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-72139afbab` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-72139afbab See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-0f36435e8e has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-0f36435e8e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0f36435e8e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-0699371c4d has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-72139afbab has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-0f36435e8e has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |