The previous versions of portage were working fine here, in nonstandard shells (the same one used by portage frontends, as kuroo), but with this new release 2.1_pre7-r3 it seems that emerge stops at the line man: , >>AUTOCLEAN never shows in emerge.log and cpu use stay to 0% for hours. The oprion used are "emerge --nospinner --nocolor packagetoemerge".... anyone has clues on what happened? Something has changed in autoclean or related tool that need some standard shell enviroment variable?
To be more clear, what doesn't starts seems to be : strip: i686-pc-linux-gnu-strip --strip-unneeded /usr/.... /usr/.... the output stops at the "man:" line.
"Shell" used is KProcIO : http://developer.kde.org/documentation/library/3.5-api/kdelibs-apidocs/kdecore/html/classKProcIO.html rollback to portage-2.1_pre3-r1 gaved me a line more in the output (than "man:"): "man: prepallstrip:" my current system has expat-2.0.0, if this can give more clues.
Some more info: perpall and prepstrip seem to be running, howerver they use 0% CPU and don't exit until I abort emerge.
I think I'm seeing the same thing. The problem seems to be scanelf. evolution ~ # strace -p `pidof scanelf` Process 12588 attached - interrupt to quit read(0, It just sits there forever. I'm trying to get it so I can capture the whole strace of it, but don't have anything yet.
Yes, you're definitely right, I did an equery b /usr/bin/scanelf , it pointed pax-utils that I updated not too long ago, so I masked pax-utils-0.1.11 and downgraded to 0.1.10. Guess what? It restarted to work fine!
What should we do now? Start a new report for pax-utils-0.1.11 titled "is so restrictive that portage frontends can't be run anymore"? Or you found this scanelf issue for some other software?
name changed to "pax-utils-0.1.11 blocks portage frontends from launching prepallstrip during emerge" to reflect what has been discovered in this report.
no one here bothered with `emerge info`
new stdin -f handling?
I would suspect Line 1242 http://sources.gentoo.org/viewcvs.py/gentoo-projects/pax-utils/scanelf.c?r1=1.131&r2=1.132
yeah that last hunk needed a little tweaking fixed in cvs, just need a new release now
fixed with 0.1.11-r1
