Edit: Original comment wanted to allow LicenseRef-ISO-8879
https://gitlab.com/fedora/legal/fedora-license-data/-/merge_requests/103/diffs says this is generally not valid, but has exceptions. Should license-validate accept it?
license-validate
I think it should, but maybe warn about it? It is, after all, a valid license in (some contexts) in Fedora.
I cannot (and do not want to) do any evaluation beyond just taking the data from fedora-license-data. If you think that this license should be validated in some scenarios then ask for that in fedora-license-data. I can imagine setting it to allowed-documentation or similar. But I am not a lawyer.
Metadata Update from @msuchy: - Issue status updated to: Closed (was: Open)
I am not clear on the next steps here. The license is already in fedora-license-data: https://gitlab.com/fedora/legal/fedora-license-data/-/blob/main/data/LicenseRef-ISO-8879.toml
And the data file includes that the license is not allowed as well as the exceptions to that rule (for character sets).
My request is that license-validate should accept it since it's listed in fedora-license-data (and optionally show that it's not allowed along with the exceptions).
Metadata Update from @omajid: - Issue status updated to: Open (was: Closed)
This tool merely exposes information from "status" field.
https://gitlab.com/fedora/legal/fedora-license-data/-/blob/main/data/LicenseRef-ISO-8879.toml#L5
It states "not-allowed".
Ahh... I see. You want me to print "not allowed" and state the reason extracted from fedora-license-data, right?
Yes, that would be great.
Running the current version of license-validate shows me this:
$ license-validate 'LicenseRef-ISO-8879' No terminal defined for 'L' at line 1 col 1 LicenseRef-ISO-8879 ^ Expecting: {'__ANON_159', '__ANON_86', '__ANON_135', '__ANON_93', 'MTLL', '__ANON_50', '__ANON_217', '__ANON_111', '__ANON_185', '__ ANON_119', '__ANON_223', '__ANON_179', '__ANON_143', 'MUP', '__ANON_15', '__ANON_48', '__ANON_196', '__ANON_248', '__ANON_36', '__AN ON_177', '__ANON_200', '__ANON_221', 'NRL', '__ANON_46', '__ANON_49', '__ANON_47', '__ANON_91', 'W3C', '__ANON_37', 'NOKIA', 'ICU', 'AMDPLPA', 'CUBE', '__ANON_171', '__ANON_20', '__ANON_239', '__ANON_212', 'TOSL', 'EPICS', '__ANON_24', 'NLPL', '__ANON_16', 'GNUPLO T', '__ANON_44', '__ANON_40', 'DOTSEQN', '__ANON_151', '__ANON_122', '__ANON_130', 'FSFULLRWD', '__ANON_230', '__ANON_117', '__ANON_ 203', 'VOSTROM', '__ANON_188', '__ANON_194', 'TMATE', '__ANON_160',
Which I now know means "not valid". But I think that since this license is in the list of not-allowed licenses (with exceptions) in Fedora, license-validate show tell me that, including the (known) exceptions.
I second this, the "not valid" message was confusing for me as well
This https://gitlab.com/fedora/legal/fedora-license-data/-/merge_requests/325 needs to be merged and released first.
Addressed in e41b474
$ ./license-validate.py -v 'LPPL-1.2 OR MIT' Warning: LPPL-1.2 is not-allowed license LPPL-1.2 can be used under this condition: Packages under the LaTeX Project Public License version 1.2 or any later version are allowed with the understanding that Fedora will treat such packages as being licensed under the LaTeX Project Public License version 1.3a or any later version. It is not necessary to include a copy of version 1.3a or to delete or replace copies of version 1.2, or to alter any notices referring to version 1.2. However, any License tag that refers to the LPPL in this situation should use `LPPL-1.3a+`, not `LPPL-1.2` (or `LPPL-1.2+`). Uses not-allowed license.
This issue has been migrated to GitHub: https://github.com/fedora-copr/license-validate/issues/10 Don't forget to subscribe for notifications about new comments.