1 |
On 02-04-2008 10:56:28 +0200, Duft Markus wrote: |
2 |
> Hi! |
3 |
> |
4 |
> ImportError: No module named portage.const |
5 |
|
6 |
^^^^ |
7 |
|
8 |
> configure: error: bad value for --with-root-user |
9 |
> |
10 |
> !!! Please attach the following file when seeking support: |
11 |
> !!! /opt/gentoo/var/tmp/portage/sys-apps/portage-2.2.00.9583/work/prefix-portage-2.2.00.9583/config.log |
12 |
> * |
13 |
> * ERROR: sys-apps/portage-2.2.00.9583 failed. |
14 |
> |
15 |
> What can i do? |
16 |
> |
17 |
> From the portage i use for bootstrap: /tools/snapshot/prefix-launcher-1pre.20080225/i586-pc-interix3.5/lib/portage/pym/portage/__init__.py:VERSION="2.2.00.8280-prefix" |
18 |
> If i change the ebuild and hardcode the root user, everything works fine. Is my bootstrap portage too old? |
19 |
|
20 |
Feels like quite ancient to me, yes, but IIRC, portage.const should |
21 |
exist there too. Does 'import portage' work with your (bootstrapped) |
22 |
python? I think it works for noone during bootstrapping actually, |
23 |
unless python (from the tree) is emerged before reinstalling portage. I |
24 |
think my bootstrap docs at least for Mac OS X and Solaris (the only two |
25 |
that are possibly correct by the way) pull in python before portage |
26 |
reemerges itself (step 1.10 in the Solaris bootstrap) hence it works |
27 |
there. Maybe that's not an option for you, then we have to make a |
28 |
workaround. |
29 |
|
30 |
|
31 |
-- |
32 |
Fabian Groffen |
33 |
Gentoo on a different level |
34 |
-- |
35 |
gentoo-alt@l.g.o mailing list |