* Messages for package sys-devel/clang-2.9: * The 'postrm' phase of the 'sys-devel/clang-2.9' package has failed with * exit value 1. * * The problem occurred while executing the ebuild file named * 'clang-2.9.ebuild' located in the '/var/db/pkg/sys-devel/clang-2.9' * directory. If necessary, manually remove the environment.bz2 file and/or * the ebuild file located in that directory. * * Removal of the environment.bz2 file is preferred since it may allow the * removal phases to execute successfully. The ebuild will be sourced and * the eclasses from the current portage tree will be used when necessary. * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm() * removal phases to be skipped entirely. * ERROR: sys-devel/clang-2.9 failed (postrm phase): * python_mod_cleanup(): python_pkg_setup() or python_execute_function() not called * * Call stack: * ebuild.sh, line 56: Called pkg_postrm * environment, line 2674: Called python_mod_cleanup 'clang' * environment, line 4144: Called die * The specific snippet of code: * die "${FUNCNAME}(): python_pkg_setup() or python_execute_function() not called"; * * If you need support, post the output of 'emerge --info =sys-devel/clang-2.9', * the complete build log and the output of 'emerge -pqv =sys-devel/clang-2.9'. * The complete build log is located at '/var/tmp/portage/._unmerge_/sys-devel/clang-2.9/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/._unmerge_/sys-devel/clang-2.9/temp/environment'. * S: '/var/tmp/portage/._unmerge_/sys-devel/clang-2.9/work/clang-2.9'
Still seeing this with clang-2.9-r1.
Not sure what is happening here, I cannot reproduce on my system (just tested with 2.9-r1, 3.0 and 9999 versions). As nothing has changed for some time in the ebuilds regarding python hanlding, this may be something changed in the eclass, but then I wonder what's different between our setups to trigger it ;)
And it's working too with 3.0. I checked python eclass usage, this should be fine and working. Can you still reproduce it with current python eclass and clang ebuilds?
Yeah, this still happens even with clang-3.0-r1.
Long gone.
