Bug 164780 is back. Updating exo from 0.3.4-r2 to 0.3.100 failed for me due to package collisions. Yes, I know I could disable them, using the protect-owned FEATURE instead of collision-protect, but that's more of a workaround than an actual fix. Detected file collision(s): /usr/lib/python2.5/site-packages/pyexo.pyo /usr/lib/python2.5/site-packages/pyexo.pyc /usr/lib/python2.5/site-packages/exo-0.3/exo/__init__.pyc /usr/lib/python2.5/site-packages/exo-0.3/exo/__init__.pyo The 0.3.4-r2 ebuild removes those files prior to installation, and a comment refers to bug 164780. I have no clue why the devs still chose to remove that portion of the ebuild.
thanks, fixed this probably slipped because I used -python when testing
*** Bug 262142 has been marked as a duplicate of this bug. ***