Hello everyone,
From Raphael:
Hopefully one the of the people who will discover this RC bug (because
their package depends on freeimage or whatever) can be convinced to take
over this package... it has been orphaned for way too long.
I am one such package maintainers (ArrayFire) affected by the autorm of
freeimage. Also, other projects I am involved with do use freeimage. I may
consider taking over the maintenance of freeimage under d-science but want
to evaluate the amount of efforts that would require first.
From Scott:
Freeimage > 1.5.4 (that is, the current sid version) requires OpenJPEG
2.1.0, which is not in Debian.
At this moment, the best course of action may be to simply carry the new
patches Raphael pointed out rather than updating freeimage then working to
remove openjpeg 2.1 support.
Which you hinted to be a non-trivial task, isn't it? Would it make things
easier if OpenJPEG was updated to 2.1.0 in Debian? I guess it would be a
requirement for a potential update of freeimage to 3.17 onwards?
Just trying to define what the "ideal" course of actions should be. I
understand the latter is currently far from reality.
Best regards,
Ghislain
--
To unsubscribe, send mail to 797165-unsubscribe@bugs.debian.org.