On Sun, 2009-09-20 at 15:26 -0500, Andrew Gaffney wrote: > On 09/20/2009 03:22 PM, Alan Hourihane wrote: > > On Sun, 2009-09-20 at 14:41 -0500, Andrew Gaffney wrote: > >> On 09/20/2009 01:13 PM, Alan Hourihane wrote: > >>> ImportError: No module named cache.metadata_overlay > >> > >> You're getting this because you're using portage-2.2_rc41 (or thereabouts), > >> which introduces a number of incompatibilities with the way that catalyst > >> assumed portage-2.1.x worked. > >> > >> You can bypass this error by removing 'metadata_overlay' from 'options' in > >> /etc/catalyst/catalyst.conf. It really doesn't even make sense to have the > >> option anymore, since portage uses it by default these days. > > > > Hi Andrew, > > > > Thanks for the response, removing that didn't seem to make much > > difference.... > > Run catalyst with -a so it clears the autoresume points.
Thanks again. Got furthur now, by switching to a stage1 seed to generate a stage2, but getting this with python... I'm wondering where the portage seed is and I can try and generate my own stage1 ?? Thanks, Alan. running build_scripts creating build/scripts-2.5 copying and adjusting /var/tmp/portage/dev-lang/python-2.5.4-r3/work/Python-2.5.4/Tools/scripts/pydoc -> build/scripts-2.5 copying and adjusting /var/tmp/portage/dev-lang/python-2.5.4-r3/work/Python-2.5.4/Tools/scripts/idle -> build/scripts-2.5 copying and adjusting /var/tmp/portage/dev-lang/python-2.5.4-r3/work/Python-2.5.4/Lib/smtpd.py -> build/scripts-2.5 changing mode of build/scripts-2.5/pydoc from 644 to 755 changing mode of build/scripts-2.5/idle from 644 to 755 changing mode of build/scripts-2.5/smtpd.py from 644 to 755 make: *** [sharedmods] Error 1 * * ERROR: dev-lang/python-2.5.4-r3 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 4011: Called die * The specific snippet of code: * emake || die "emake failed" * The die message: * emake failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-lang/python-2.5.4-r3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lang/python-2.5.4-r3/temp/environment'. *
