Great breakage with exactly zero value...
(In reply to Lars Wendler (Polynomial-C) from comment #1)
> Great breakage with exactly zero value...
I wasn't expecting senseless comment on a Tracker from a developer, but needless to say, no talking in the Tracker.
What I usually try to find in such trackers is the canonical
way of fixing known widespread breakages. And always fail.
One of them seems to be related to bool / boolean type
difference in g-4.7+ (C++ code only?):
which basically means (taken from webkit breakage)
> - if (jpeg_read_header(&m_info, true) == JPEG_SUSPENDED)
> + if (jpeg_read_header(&m_info, TRUE) == JPEG_SUSPENDED)
added multilib and security patched jpeg-8d-r1 since there are so many jpeg-9 bugs left here
Anyone following this bug:
I could really use some help with the open bugs, like bug 520674 for which I have repeatedly failed to provide a patch to
what did happen finally with this breakage? Do we plan to use jpeg-9 ever in stable... I am unsure if broken reverse deps are now "working" simply because most of us are using jpeg-turbo and, hence, not hitting this :/
I also doubt jpeg-9 will ever get used as it seems that release was really controversial... :/, I was wondering if we should simply remove it :|
I guess we can close this finally.