Bug 1003416 - uniconvertor included non-free files.
Summary: uniconvertor included non-free files.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: uniconvertor
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Alexeev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: FE-Legal
TreeView+ depends on / blocked
 
Reported: 2013-09-01 23:43 UTC by mejiko
Modified: 2013-09-12 01:56 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-03 21:06:11 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Debian BTS 699301 0 None None None Never

Description mejiko 2013-09-01 23:43:06 UTC 
Hello.

uniconvertor included non-free files. See debian bug number "699301" datails.
I think that this package be affected by debian bug number "699301".


Suggests:

1. Remove non-free code, and rebuild.

2. Replace fedora free (Fedora acceptable licensed) files.

3. Remove fedora repos.


Thanks.


Reference:

http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=699301
Comment 1 mejiko 2013-09-01 23:43:42 UTC 
Blocking FE-Legal, This is license problem.
Comment 2 Pavel Alexeev 2013-09-02 08:03:27 UTC 
Thanks. I have asked upstream byt mail.
Comment 3 Tom "spot" Callaway 2013-09-03 21:06:11 UTC 
I've applied a fix in rawhide (and f20) to use the argyllcms sRGB.icm. You might want to ask upstream to use that file instead.
Comment 4 Pavel Alexeev 2013-09-04 15:25:44 UTC 
Thanks.
Comment 5 Fedora Update System 2013-09-08 19:59:33 UTC 
uniconvertor-2.0-0.2.svn344.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/uniconvertor-2.0-0.2.svn344.fc19
Comment 6 Fedora Update System 2013-09-12 01:56:38 UTC 
uniconvertor-2.0-0.2.svn344.fc19 has been pushed to the Fedora 19 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.