On Sunday 20 June 2010 16:05:58 Alex Schuster wrote:
> meino.cramer@gmx.de writes:
> > Alex Schuster <wonko@wonkology.org> [10-06-20 15:16]:
> >> How about putting dev-python/setuptools into
> >> /etc/portage/package.keywords, and trying to emerge 0.6.13?
> >
> > I tried to re-emerge setuptools 0.6.10 and it fails the same way.
> > So I believe (=not knowing) that this problem is caused by something
> > outside setuptools, which gets screwed up.
> 
> Probably python itself, as Arttu pointed out.
> 
> > Problem with 0.6.13 is: If it compiles and installs itsself, 0.6.10
> > (current version) is gone and cannot get back due to the same problem
> > (see above). And then I have a "unstable" version, which may pull in
> > other unstable versions of something else, which pull in....
> 
> Maybe, but at least in the ebuild itself there are no such dependencies.
> If you'd need to keyword this package only, it should do no harm. If
> more things need to be keyworded, I agree that this tends to make things
> complicated. But at least you can quickpkg the existing version, and get
> it back when needed without compiling with emerge -k.
> But when 0.6.10 also fails, the problem is likely to be somewhere else.
> 
> > This way I have corrupted my last installed gentoo system...
> 
> I'm at ~amd64 now, and things are easier now :) At least for me.
> 
> If you are desperate: Maybe removing setuptools would at least make
> python-updater run through, unless something would pull it in again.
> Emerge -k setuptools back. You may be missing stuff for python 3.1, but
> maybe this does not harm too much.
> 
> And report a bug at bugs.gentoo.org, so the maintainers know what's
> going on.

I'd have another go but after setting MAKEOPTS="-j1" (although I have to admit 
the error you posted does not look like this would make any difference).
-- 
Regards,
Mick