Bug 1570201 - Bad License: tag for uboot-tools
Summary: Bad License: tag for uboot-tools
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: uboot-tools
Version: 27
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1577465 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-20 22:02 UTC by Artur Frenszek-Iwicki
Modified: 2018-11-30 21:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 21:35:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Artur Frenszek-Iwicki 2018-04-20 22:02:43 UTC
The License: tag for uboot-tools is "GPLv2+ BSD LGPL-2.1+ LGPL-2.0+". This contradicts the Licensing Guidelines, which say that in multiple-licensing scenarios, the words "and" & "or" must be used to describe the relationship between the licences.
https://fedoraproject.org/wiki/Packaging:LicensingGuidelines#Dual_Licensing_Scenarios

Also, the Licensing page on the wiki says to use "LGPLv2+" as the identifier for both LGPL-2.0+ and LGPL-2.1+.
https://fedoraproject.org/wiki/Licensing:Main#Good_Licenses

Comment 1 Peter Robinson 2018-05-12 09:01:29 UTC
*** Bug 1577465 has been marked as a duplicate of this bug. ***

Comment 2 Dennis Gilmore 2018-05-13 14:41:38 UTC
I would almost say this is not a bug, different files inside of teh source tree have different licenses, depending on the configuration of the different firmware images you are bound to get different combinations per file within the rpms, you could not correctly have a blanket statement for the entire package, it is just not black and white like that.

Comment 3 Peter Robinson 2018-05-14 11:29:04 UTC
I think we likely need to tweak the AND/OR nomenclature in the licensing but as Dennis mentioned it's complex and I've not had the time to review it because it's been in this state for _YEARS_ and I've had more important things that have been demanding my attention.

If someone wants to suggest what they believe it should be changed to with their documented reasoning/logic I will happily review it but atm it's quite low on my todo list.

Comment 4 Ben Cotton 2018-11-27 15:43:06 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2018-11-30 21:35:35 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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