Bug 848875 - dom4j: possibly contains non-free documentation
Summary: dom4j: possibly contains non-free documentation
Alias: None
Product: Fedora
Classification: Fedora
Component: dom4j
Version: 18
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Mikolaj Izdebski
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2012-08-16 16:30 UTC by Mikolaj Izdebski
Modified: 2012-12-01 09:54 UTC (History)
3 users (show)

Fixed In Version: 1.6.1-11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-12-01 09:53:58 UTC
Type: Bug

Attachments (Terms of Use)

Description Mikolaj Izdebski 2012-08-16 16:30:56 UTC
xml-apis-2.0.2.jar contains LICENSE.dom-documentation.txt, which states:
> Copyright © 1994-2001 World Wide Web Consortium

This license is not allowed in Fedora, see:

I'm not sure if this license actually covers any documentation included in binary packages, but the jar file that contains it is removed in %prep.
If there is any non-free documentation, please remove it from Fedora.
Otherwise please remove the license file as it doesn't apply and only causes confusion.

Comment 1 Hans de Goede 2012-08-18 09:10:03 UTC
Thanks for reporting this! I've discussed this with Tom Callaway, and since the files in question are
not actual distributed other then as part of the src.rpm, This is not an issue:

On 08/17/2012 09:32 AM, Hans de Goede wrote:
> Hi Spot,
> Someone has brought it to my attention that one of the dependency jars
> bundled with dom4j contains W3C Documentation Licensed files:
> https://bugzilla.redhat.com/show_bug.cgi?id=848875
> (sigh java upstreams are terrible with all their bundled jars)
> The first thing %prep does is blow these jars away, and the rest
> of the build uses system versions of the jars in question, so the
> files in there are not used at all.
> Given that according to:
> http://fedoraproject.org/wiki/Licensing:Main#Bad_Licenses_2
> the problem with the W3C doc license is "Does not permit modification",
> I was wondering if it is necessary to create a cleaned-up sources
> tarbal for dom4j for this, or if things are ok as is?

Nope, this is fine. There is no restriction on redistribution, thus a
"clean" source tarball is not required (although, if you want to do it,
you can).



Closing this as not a bug.

Comment 2 Mikolaj Izdebski 2012-08-20 07:47:56 UTC
I think it still would be better to remove copyright notices and license files that don't apply to any material in SRPM, especially if they are non-free.

Comment 3 Hans de Goede 2012-08-20 08:47:13 UTC
I'm not going to stop you from:

1) Writing a cleanup-sources.sh script to generate a -clean.tar.gz from the original upstream tarbal
2) replace Source0 with a newly generated -clean.tar.gz and add cleanup-sources.sh as Source1
3) commit and build the above for rawhide.

If you don't have commit access to dom4j , feel free to ask for it in pkgdb and I'll grant it.

But I simply don't have the time to do this myself atm.

Comment 4 Mikolaj Izdebski 2012-08-20 08:54:06 UTC
(In reply to comment #3)
> I'm not going to stop you from:

Not having commit right was stopping me.
But I will request it and fix the bug.

Comment 7 Tom "spot" Callaway 2012-08-21 12:28:08 UTC
Not actually a legal blocker, so I'm lifting FE-Legal here, feel free to fix the bug though. :)

Comment 8 Fedora Update System 2012-10-29 16:14:53 UTC
dom4j-1.6.1-11.fc18 has been submitted as an update for Fedora 18.

Comment 9 Fedora Update System 2012-10-29 18:15:48 UTC
Package dom4j-1.6.1-11.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dom4j-1.6.1-11.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2012-12-01 09:54:00 UTC
dom4j-1.6.1-11.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

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