Bug 2219549 - Missing license in the License field
Summary: Missing license in the License field
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora
Classification: Fedora
Component: tss2
Version: 39
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jerry Snitselaar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-04 09:21 UTC by Štěpán Horáček
Modified: 2023-08-16 08:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Štěpán Horáček 2023-07-04 09:21:45 UTC
The spec file's License field does not contain the Trusted Computing Group license, even though the license file does contain it.

Reproducible: Always

Steps to Reproduce:
1. List the licenses (e.g. by using `rpm -q tss2 --queryformat "%{license}\n"`).
Actual Results:  
BSD

Expected Results:  
BSD and TCGL

Comment 1 Štěpán Horáček 2023-07-04 09:30:11 UTC
There is a relevant GitLab issue for adding the license as allowed in Fedora: https://gitlab.com/fedora/legal/fedora-license-data/-/issues/24

Comment 2 Jerry Snitselaar 2023-07-05 16:13:31 UTC
It looks like it should be:

License: BSD-3-Clause AND TCGL

One thing I just noticed though is that the TCGL isn't listed on the SPDX website license list [1].

[1] https://spdx.org/licenses/

Comment 3 Štěpán Horáček 2023-07-07 11:13:17 UTC
Thank you for the correction. Using the SPDX format instead of the legacy one makes more sense.

TCGL not being listed is part of the problem. Originally, it was not added because the only package listing it as their license was tpm2-tss, which listed it erroneously. I would think adding it is a part of the GitLab issue I linked.

Comment 4 Fedora Release Engineering 2023-08-16 08:11:54 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.


Note You need to log in before you can comment on or make changes to this bug.