1 |
On Sun, 2009-09-20 at 15:26 -0500, Andrew Gaffney wrote: |
2 |
> On 09/20/2009 03:22 PM, Alan Hourihane wrote: |
3 |
> > On Sun, 2009-09-20 at 14:41 -0500, Andrew Gaffney wrote: |
4 |
> >> On 09/20/2009 01:13 PM, Alan Hourihane wrote: |
5 |
> >>> ImportError: No module named cache.metadata_overlay |
6 |
> >> |
7 |
> >> You're getting this because you're using portage-2.2_rc41 (or thereabouts), |
8 |
> >> which introduces a number of incompatibilities with the way that catalyst |
9 |
> >> assumed portage-2.1.x worked. |
10 |
> >> |
11 |
> >> You can bypass this error by removing 'metadata_overlay' from 'options' in |
12 |
> >> /etc/catalyst/catalyst.conf. It really doesn't even make sense to have the |
13 |
> >> option anymore, since portage uses it by default these days. |
14 |
> > |
15 |
> > Hi Andrew, |
16 |
> > |
17 |
> > Thanks for the response, removing that didn't seem to make much |
18 |
> > difference.... |
19 |
> |
20 |
> Run catalyst with -a so it clears the autoresume points. |
21 |
|
22 |
Thanks again. |
23 |
|
24 |
Got furthur now, by switching to a stage1 seed to generate a stage2, but |
25 |
getting this with python... |
26 |
|
27 |
I'm wondering where the portage seed is and I can try and generate my |
28 |
own stage1 ?? |
29 |
|
30 |
Thanks, |
31 |
|
32 |
Alan. |
33 |
|
34 |
running build_scripts |
35 |
creating build/scripts-2.5 |
36 |
copying and |
37 |
adjusting /var/tmp/portage/dev-lang/python-2.5.4-r3/work/Python-2.5.4/Tools/scripts/pydoc -> build/scripts-2.5 |
38 |
copying and |
39 |
adjusting /var/tmp/portage/dev-lang/python-2.5.4-r3/work/Python-2.5.4/Tools/scripts/idle -> build/scripts-2.5 |
40 |
copying and |
41 |
adjusting /var/tmp/portage/dev-lang/python-2.5.4-r3/work/Python-2.5.4/Lib/smtpd.py -> build/scripts-2.5 |
42 |
changing mode of build/scripts-2.5/pydoc from 644 to 755 |
43 |
changing mode of build/scripts-2.5/idle from 644 to 755 |
44 |
changing mode of build/scripts-2.5/smtpd.py from 644 to 755 |
45 |
make: *** [sharedmods] Error 1 |
46 |
* |
47 |
* ERROR: dev-lang/python-2.5.4-r3 failed. |
48 |
* Call stack: |
49 |
* ebuild.sh, line 49: Called src_compile |
50 |
* environment, line 4011: Called die |
51 |
* The specific snippet of code: |
52 |
* emake || die "emake failed" |
53 |
* The die message: |
54 |
* emake failed |
55 |
* |
56 |
* If you need support, post the topmost build error, and the call stack |
57 |
if relevant. |
58 |
* A complete build log is located at |
59 |
'/var/tmp/portage/dev-lang/python-2.5.4-r3/temp/build.log'. |
60 |
* The ebuild environment file is located at |
61 |
'/var/tmp/portage/dev-lang/python-2.5.4-r3/temp/environment'. |
62 |
* |