Bug 817646 - kxml: incorrect License tag
Summary: kxml: incorrect License tag
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kxml
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mikolaj Izdebski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-30 18:07 UTC by Mikolaj Izdebski
Modified: 2012-07-22 09:07 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-07-22 09:07:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Patch fixing the problem (1.62 KB, patch)
2012-04-30 18:07 UTC, Mikolaj Izdebski 		no flags Details | Diff
View All

Description Mikolaj Izdebski 2012-04-30 18:07:00 UTC 
Created attachment 581240 [details]
Patch fixing the problem

The License tag of kxml states BSD, but the license.txt file contains MIT license. Therefore the correct tag value should be MIT.

Patch fixing the problem is included.
Comment 1 Mikolaj Izdebski 2012-04-30 18:16:49 UTC 
Also I noticed that kxml2-2.2.2.pom refers to the license as BSD. It also links to a license text different from what is included in license.txt.

I'm blocking FE-Legal because the licensing situation is unclear.
Comment 2 Alexander Kurtakov 2012-04-30 18:18:53 UTC 
Patch applied http://koji.fedoraproject.org/koji/taskinfo?taskID=4036255
Comment 3 Alexander Kurtakov 2012-04-30 18:22:04 UTC 
The pom file is coming from third party so I don't think it should matter in this case. We can easily remove it, change it or even generate one ourselves. I would ask you or legal team to remove the block.
Comment 4 Tom "spot" Callaway 2012-04-30 18:24:05 UTC 
The licensing in the POM file is incorrect, you should advise upstream of this, but it is not a blocker issue for Fedora. Lifting FE-Legal.
Comment 5 Fedora Admin XMLRPC Client 2012-04-30 18:27:05 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 6 Mikolaj Izdebski 2012-07-22 09:07:07 UTC 
Fixed in 2.2.2-11
Note You need to log in before you can comment on or make changes to this bug.