[Gnewsense-dev] Bug #35790 (fop related) and the way of fixing it

[Marek Buras]

Hey list!

Last night I looked at that #35790 bug report. While looking for information
I found that it has been reported upstream[1] and someone mentioned that there
is Argyll Color Management System[2] which provides tools for managing ICM
profiles. It's even better - there is ready to use sRGB profile in the source
tarball for latest ArgyllCMS release which I think is placed in the public
domain (whole project is on AGPL3).

Looking through $(hexdump -C sRGB.icm) I have found these informations:

000001a0  00 00 00 00 00 3f 73 52  47 42 20 49 45 43 36 31  |.....?sRGB IEC61|
000001b0  39 36 36 2d 32 2e 31 20  28 45 71 75 69 76 61 6c  |966-2.1 (Equival|
000001c0  65 6e 74 20 74 6f 20 77  77 77 2e 73 72 67 62 2e  |ent to www.srgb.|
000001d0  63 6f 6d 20 31 39 39 38  20 48 50 20 70 72 6f 66  |com 1998 HP prof|
000001e0  69 6c 65 29 00 00 00 00  00 00 00 00 74 65 78 74  |ile)........text|
000001f0  00 00 00 00 50 75 62 6c  69 63 20 44 6f 6d 61 69  |....Public Domai|
00000200  6e 2e 20 4e 6f 20 57 61  72 72 61 6e 74 79 2c 20  |n. No Warranty, |
00000210  55 73 65 20 61 74 20 6f  77 6e 20 72 69 73 6b 2e  |Use at own risk.|

Is it ok to just replace non-free ICM with this one and provide package with
modified sources? Or it's better to wait for upstream until they solve the
problem there? The bug is open upstream since 2012-02-18.

If it's ok, I can rebuild this package (actually I've done it already, but it's
still proof of concept).

[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=52704
[2] http://www.argyllcms.com/

-- 
Marek Buras
cyfr0n (at) go2.pl