Hi. This is more of a request than a bug that the jpeg-compat package receive a bit more attention either by means of a news item or some adjusted use-flags / dependencies. My issue arose when I went through the update from jpeg 6x to 7 and later tried to compile qt-3.x which failed miserably as it looks for libjpeg.so.62. In the interest of making things easier for users so they don't have to dig through error logs and spend a couple hours searching for a solution putting up a news item about the jpeg transition would be fantastic. Alternately I guess this could be solved by editing the use flag around the qt library or the jpeg ebuild to include something like 'jpeg62support' which would pull in the compat package. Reproducible: Always Steps to Reproduce:
You shouldn't need the compat package at all - just run revdep-rebuild from the app-portage/gentoolkit package.
(In reply to comment #1) > You shouldn't need the compat package at all - just run revdep-rebuild from the > app-portage/gentoolkit package. > I wish that were the case but revdep-rebuild provided nothing. Every time it attempted to pull in qt-3 on its own and my qt-3.x statically looks for /usr/lib/libjpeg.so.62 which jpeg-7 does not provide. qt-3.x also doesn't restrict jpeg versions as being < 7 so it doesn't know to pull a slotted version or put a block up (I'm not sure if jpeg-6 blocks jpeg-7). Either way x11-libs/qt failed compilation after jpeg-7 every time until I manually pulled in the jpeg-compat package.
*** Bug 288757 has been marked as a duplicate of this bug. ***
Did you run `lafilefixer --justfixit' too?
(In reply to comment #4) > Did you run `lafilefixer --justfixit' too? > Can't say that I did. In fact until now, I'd never even heard of that tool.
OK, please emerge lafilefixer and try the command in my last comment. It should fix the problem and a lot more potential problems.
Qt 3.x works with jpeg-7. jpeg-compat is ONLY for binary-only packages.
