'emerge -p --depclean' suggested to remove python-exec-0.3.1. After removal I now have still python-exec-2.0-r2. But now several packages as layman, java-config-wrapper and java-config are now broken, because their binaries are links to /usr/bin/python-exec: root@condor:/root(38)# ll /usr/bin/layman lrwxrwxrwx 1 root root 11 Jul 29 14:13 /usr/bin/layman -> python-exec* root@lynx:/root(14)# ll /usr/bin/depend-java-query lrwxrwxrwx 1 root root 11 Sep 6 10:32 /usr/bin/depend-java-query -> python-exec But there is no /usr/bin/python-exec in python-exec-2.0-r2: root@lynx:/root(17)# qlist python-exec /usr/share/doc/python-exec-2.0-r2/NEWS.bz2 /usr/lib/python-exec/python-exec2-c /usr/lib/python-exec/python-exec2 root@lynx:/root(18)# qlist -Iv python-exec dev-python/python-exec-2.0-r2 Manual reeemerging of layman, java-config-wrapper and java-config solved the issue so far. But the issue is not detected by 'emerge @preserved-rebuild' or 'revdep-rebuild'. So it would be good if it would solved autoamically by one of these two methods in future. Reproducible: Always
*** This bug has been marked as a duplicate of bug 489440 ***
The next package is javatoolkit-0.3.0-r9: root@lynx:/root(23)# ll /usr/lib64/javatoolkit/bin/xml-rewrite-2.py lrwxrwxrwx 1 root root 24 Sep 14 11:21 /usr/lib64/javatoolkit/bin/xml-rewrite-2.py -> ../../../bin/python-exec root@lynx:/root(24)# qfile -v /usr/lib64/javatoolkit/bin/xml-rewrite-2.py dev-java/javatoolkit-0.3.0-r9 (/usr/lib64/javatoolkit/bin/xml-rewrite-2.py)
