1 |
Trying to upgrade portage in an older embedded target I get:
|
2 |
When upgrading from old 2.3.62
|
3 |
>>> Merging sys-apps/portage-2.3.65 to /
|
4 |
/usr/bin/python3.4: Error while finding spec for 'portage._compat_upgrade.default_locations' (<class 'ImportError'>: No module named 'portage._compat_upgrade')
|
5 |
* ERROR: sys-apps/portage-2.3.65::tmv3-target-overlay failed (preinst phase):
|
6 |
* (no error message)
|
7 |
*
|
8 |
* Call stack:
|
9 |
* ebuild.sh, line 133: Called pkg_preinst
|
10 |
* environment, line 3193: Called die
|
11 |
* The specific snippet of code:
|
12 |
* env -u DISTDIR -u PORTAGE_OVERRIDE_EPREFIX -u PORTAGE_REPOSITORIES -u PORTDIR -u PORTDIR_OVERLAY PYTHONPATH="${D%/}${PYTHON_SITEDIR}${PYTHONPATH:+:${PYTHONPATH}}" "${PYTHON}" -m portage._compat_upgrade.default_locations || die;
|
13 |
*
|
14 |
|
15 |
Not a python expert but isn't portage trying to use a new function in portage(portage._compat_upgrade.default_locations) before
|
16 |
it is installed?
|
17 |
|
18 |
How should I resolve this?
|
19 |
|
20 |
|
21 |
Jocke |