Updating releaseforge from 1.1 to 1.3 failed for me due to package collisions. Yes, I know I could disable them, but that's more of a workaround than a fix. Instead I looked at bug 176612 which seems to be a similar case. There the conclusion was to disable the generation of the *.pyo files in the ebuild. The reason why 1.3 builds *.py where 1.1 did not is the addition of the line "optimize = 1" to the [install] section of setup.cfg. Solutions would be to either patch that line or, easier still, pass --optimize=0 to setup.py via distutils_src_install. I'll attach a patch to the ebuild. You might also consider always passing that option in distutils.eclass, if indeed optimized versions should never compiled by the ebuild itself. I don't realls understand this whole setup of Python in Gentoo. Seems like an awful lot would happen outside the sandbox, and I don't know why. You could also say that the *.pyo files should in fact get installed by the ebuild itself. In this case, you should at least offer a message to the user that collisions for these files are to be expected, and how to disable collision checks for just that one ebuild.
Created attachment 163215 [details, diff] pass --optimize=0 to setup.py
releaseforge was removed from Portage at the same time with PyQt, so closing...
