Bug 479818 – [TRACKER] >=media-libs/jpeg-9a porting

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Julian Ospald 2013-08-05 10:54:26 UTC]

.

[Comment 1 Lars Wendler (Polynomial-C) (RETIRED) 2013-08-05 11:00:39 UTC]

Great breakage with exactly zero value...

[Comment 2 Samuli Suominen (RETIRED) 2013-08-05 11:56:28 UTC]

(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.

[Comment 3 Sergei Trofimovich (RETIRED) 2013-10-12 04:24:34 UTC]

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)

[Comment 4 Samuli Suominen (RETIRED) 2014-01-24 11:52:15 UTC]

added multilib and security patched jpeg-8d-r1 since there are so many jpeg-9 bugs left here

[Comment 5 Samuli Suominen (RETIRED) 2014-09-18 04:58:13 UTC]

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

[Comment 6 Pacho Ramos 2016-11-30 13:06:28 UTC]

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 :/

[Comment 7 Pacho Ramos 2016-11-30 13:10:45 UTC]

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 :|

[Comment 8 Andreas Sturmlechner 2018-02-12 21:40:14 UTC]

I guess we can close this finally.