Several applications will no longer install with above errors. So far, these programs have failed: hal, kipi-plugins, gimp-2.6, digikam, kdiff3, krecipes, amarok, kpowersave, kid3, kflickr, tellico, libxcb, gnome-doc-utils, ktraynetworker, and gwenview. May be others. More descriptive outline of problem in supplied url. I have re-emerged libxml2 and libxslt, python, ran python-updater, tried emerge -e system and got through most of it before I gave up with all the above failed emerges. Reproducible: Always Steps to Reproduce: 1. emerge -av1 <package> 2. 3. Actual Results: fails with: make[3]: Entering directory `/var/tmp/portage/media-gfx/digikam-0.9.4/work/digikam-doc-0.9.4/doc/digikam' /usr/kde/3.5/bin/meinproc --check --cache index.cache.bz2 ./index.docbook Warning: program compiled against libxml 207 using older 206 make[3]: *** [index.cache.bz2] Error 1 make[3]: Leaving directory `/var/tmp/portage/media-gfx/digikam-0.9.4/work/digikam-doc-0.9.4/doc/digikam' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/media-gfx/digikam-0.9.4/work/digikam-doc-0.9.4/doc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/media-gfx/digikam-0.9.4/work/digikam-doc-0.9.4' make: *** [all] Error 2 * * ERROR: media-gfx/digikam-0.9.4 failed. Expected Results: successful install Now I cannot run revdep-rebuild successfully because it fails on some of these packages. Other packages I wish to use are not installable.
1) Please post your `emerge --info' too. 2) You will need to finish a `revdep-rebuild -i' somehow. 3) This still doesn't look like one specific bug to me.
(In reply to comment #1) > 1) Please post your `emerge --info' too. > 2) You will need to finish a `revdep-rebuild -i' somehow. > 3) This still doesn't look like one specific bug to me. > apologies due: this was due to an ebuild (unsupported software) that I'm told was not sandboxed properly so leaked libraries. Vmware-vix is the culprit and it leaked its libxml2, an older version than was installed in the proper library directory. I uninstalled vmware-vix and things are back to working normally. Should this bug be marked invalid of just fixed? Here is what told the story (pardon the line-wrapping if it happens): qfile -v `locate libxml2.so` app-emulation/vmware-vix-1.6.0.116503 (/opt/vmware/server/lib/vmware-vix/lib/libxml2.so.2.6.26) app-emulation/vmware-vix-1.6.0.116503 (/opt/vmware/server/lib/vmware-vix/lib/libxml2.so.2) app-emulation/vmware-vix-1.6.0.116503 (/opt/vmware/server/lib/vmware-vix/lib/VIServer-2.0.0/32bit/libxml2.so.2.6.26) app-emulation/vmware-vix-1.6.0.116503 (/opt/vmware/server/lib/vmware-vix/lib/VIServer-2.0.0/32bit/libxml2.so.2) app-emulation/vmware-vix-1.6.0.116503 (/opt/vmware/server/lib/vmware-vix/lib/libxml2.so)
Should be marked invalid, really. :)
