KDE applications using python fail during configure phase with sandbox error (log taken from /var/log/sandbox/sandbox*.log): unlink: /usr/lib/python2.6/site-packages/PyKDE4/__init__.pyc unlink: /usr/lib/python2.6/site-packages/PyKDE4/pykdeconfig.pyc The root cause is wrong pyc - it is not generated in pkg_postinst of pykde4's ebuild, but during build, so it contains reference to original python source file /var/tmp/portage... Workaround for this is to modify ebuild - do not install those pyc files, but generate them via python_mod_optimize.
Created attachment 177238 [details] Updated ebuild containing partial workaround for python-2.6 The workaround in attached patch fixes pyc files in /usr/lib/python*/site-packages/PyKDE4/* only. There are more pyc files that probably need to be fixed too (located at /usr/kde/4.2/share/apps/pykde4, if you do use "kdeprefix" USE flag).
I forgot to note that this is python-2.6 problem, python-2.5 looks like it is happy.
Created attachment 177248 [details] Updated ebuild containing partial workaround for python-2.6 Added python clean-up part
Created attachment 177252 [details] Updated ebuild with workaround - simplified to utilize fix from bug #253593 With the fix from bug #253593 the python_version function can be used again.
Post diff please please, it is hell to work throught pasted ebuild and our ones since we might update them and we dunno what changed and what not. Thanks
Created attachment 177270 [details, diff] Patch for ebuild - simplified one
The changes are only in new methods src_install, pkg_postinst and pkg_postrm.
(In reply to comment #5) > Post diff please please, it is hell to work throught pasted ebuild and our ones > since we might update them and we dunno what changed and what not. > Thanks When using distributed version control, there should be no such problems like that. Just `git stash`, copy my version in your tree and you will see the changes via gitk (assumes you are using kde-testing via git).
On overlay -> fixored.
