On my ~amd64 (and portage-2.2) system, I recently updated media-libs/x264 from version 0.0.20111017 to 0.0.20111218. This installed the library /usr/lib64/libx264.so.119 and changed the "default version" symlink: /usr/lib64/libx264.so -> libx264.so.119 Since I have portage-2.2, the old library (.118) was still kept around. Then I remerged all packages still linking to .118 so it could then be deleted. This worked for all packages but media-video/ffmpeg-0.9 which still linked against .118 afterwards. Manually (re)moving the .118-library and then re-emerging ffmpeg worked. Reproducible: Always
Please post your `emerge --info' output too.
Created attachment 296675 [details] "emerge --info media-video/ffmpeg" from host ayanta Yes, sorry, forgot that. Info from first host. Meanwhile, I deleted the old x264 so.118 and re-emerged ffmpeg
Created attachment 296677 [details] "emerge --info media-video/ffmpeg" from host mio emerge --info from the other host. I just saw that x264-0.0.20111220 is out. Let's see wether there is a new .so-file (.120?) and how that behaves :)
Ok, here's news: I updated from x264-0.0.20111218 to x264-0.0.20111220. That introduced a new .so file ending with .120. Portage detected it correctly and told me that packages needed to be rebuilt. I rebuilt all packages but ffmpeg and verified with revdep-rebuild that only ffmpeg needed the .119-library. Then I rebuilt ffmpeg and this time it used the new library (.120) and portage deleted the old one. So everything is fine and I close this bug as OBSOLETE
