For some reason, the new portage is breaking the kde cvs ebuilds. For example, when I try to "emerge -d koffice-5": 1)It sucessfully pulls the koffice cvs tree. 2)It sucessfully copies it to the proper temp directory. 3)It sucessfully updates the kde-common cvs tree. 4)It sucessfully(?) copies it to the work/koffice dir. 5)It fails after testing for '[' -f Makefile ']' and '[' -f config.cache ']' complaining that src_unpack failed. Also, it isn't honoring the noclean flag, so that is why there is a ? in #4 (i'm still pretty sure it suceeds though). It was working with earlier versions of portage. I have tried my best to debug the script, but it just doesn't make sense why it is failing, because the bebug output show that it suceeds at every point, but then it just stops. Also, I have tried a couple of other kde cvs ebuilds, all with the same results.
Could you please send me the output of this? Also, please attach /var/tmp/portage/.../temp/eclass-debug.log. That's a very verbose log generated by all eclass-using ebuilds, which can show us precisely where (and hopefully why) the emerge process stops.
Well portage 2.0.31 has fixed this issue, so I'm closing it out.
