The openmotif-2.2.2 ebuilds are no longer in the portage tree. This creates a major problem if you have previously emerged openmotif-2.2.2 and built applications with it. emerge -U world downgrades openmotif to 2.1.3, thereby removing libXm.so.3 and replacing it with libXm.so.2. Subsequently, all applications built with libXm.so.3 are broken. Rebuilding libXm.so.3 is impossible, because the 2.2.2 ebuild is no longer in portage. Even emerge -k from a binary package does not work, because the ebuild is missing. I was lucky to have a binary package, extracted it manually and ran env-update, so my system is working again. But I thought this should get fixed before more people run into serious problems. I suggest the ebuilds are put back in portage (at least in unstable if there would be some problem). And maybe the 2.1.3 ebuild could be taught to give a warning and not to remove libXm.so.3 in the cleaning phase. Reproducible: Always Steps to Reproduce: 1. 2. 3.
please use revdep-rebuild and take a look at bug #29388
