Summary: | /sbin/ldconfig: /usr/lib/libjpeg.so.62 is not a symbolic link | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Timothy Miller <theosib> |
Component: | Current packages | Assignee: | Gentoo Graphics Project <graphics+disabled> |
Status: | VERIFIED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Timothy Miller
2009-09-16 12:25:17 UTC
I can't see this here. Can you post qlist and ls outputs? # emerge portage-utils # qlist -CIv media-libs/jpeg # ls -ld /usr/lib/libjpeg* That said, correct path is to revdep-rebuild and/or emerge @preserved-rebuild before emerging media-libs/jpeg-compat. # emerge -C jpeg-compat # revdep-rebuild (until everything is fixed) # emerge -1 jpeg-compat Mike, can you shed some light into this? You said the symlink isn't necessary, so I made an effort on not installing it from jpeg-compat. you'd get this warning if you're still using the old jpeg-compat. this should be fixed with the newer ebuild that deletes the .so.62.0.0 file. Timothy, can you verify that rebuilding media-libs/jpeg-compat and/or deleting libjpeg.so.62.0.0 makes the warning disappear? i didn't revbump the package, but appearently i should have # qlist -CIv media-libs/jpeg media-libs/jpeg-7 media-libs/jpeg-compat-6b # ls -ld /usr/lib/libjpeg* -rw-r--r-- 1 root root 306316 Aug 23 09:56 /usr/lib/libjpeg.a -rw-r--r-- 1 root root 915 Sep 15 16:50 /usr/lib/libjpeg.la lrwxrwxrwx 1 root root 16 Aug 23 09:56 /usr/lib/libjpeg.so -> libjpeg.so.7.0.0 -rwxr-xr-x 1 root root 145944 Sep 15 16:37 /usr/lib/libjpeg.so.62 -rwxr-xr-x 1 root root 145952 Sep 15 16:37 /usr/lib/libjpeg.so.62.0.0 lrwxrwxrwx 1 root root 16 Aug 23 09:56 /usr/lib/libjpeg.so.7 -> libjpeg.so.7.0.0 -rwxr-xr-x 1 root root 227920 Aug 23 09:56 /usr/lib/libjpeg.so.7.0.0 Interestingly, when I unmerged jpeg-compat and did revdep-rebuild, it didn't re-emerge any package, as though there are no deps. I had done a depclean, so I don't know why it's even in there. When I emerge -1, I don't get a complaint. This is what ls tells me now: # ls -ld /usr/lib/libjpeg* -rw-r--r-- 1 root root 306316 Aug 23 09:56 /usr/lib/libjpeg.a -rw-r--r-- 1 root root 915 Sep 15 16:50 /usr/lib/libjpeg.la lrwxrwxrwx 1 root root 16 Aug 23 09:56 /usr/lib/libjpeg.so -> libjpeg.so.7.0.0 -rwxr-xr-x 1 root root 145944 Sep 16 14:17 /usr/lib/libjpeg.so.62 lrwxrwxrwx 1 root root 16 Aug 23 09:56 /usr/lib/libjpeg.so.7 -> libjpeg.so.7.0.0 -rwxr-xr-x 1 root root 227920 Aug 23 09:56 /usr/lib/libjpeg.so.7.0.0 Does that look right? Yes, it looks right. Is the problem gone now? And you don't need jpeg-compat at all if nothing is pulling it in, it's a hack for binary only packages. As far as I can tell, the warning is gone. But I don't know which package I was emerging that triggered it. Odd. I don't have jpeg-compat in my world file, and there are no dependencies (apparently), but emerge --depclean doesn't try to remove it. Any idea why? (In reply to comment #7) > Odd. I don't have jpeg-compat in my world file, and there are no dependencies > (apparently), but emerge --depclean doesn't try to remove it. Any idea why? > apparently? revdep-rebuild might not detect them because binary pkgs are installed in /opt which it doesn't necessarily scan.. can't think of any other reason... anyway, closing, since it works for you now please do the revbump so other people dont hit the warnings. the warning on my system was what clued me into the duplication in the first place. (In reply to comment #9) > please do the revbump so other people dont hit the warnings. the warning on my > system was what clued me into the duplication in the first place. > done |