public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* [gentoo-portage-dev] Portage upgrade from 2.3.62  to 2.3.65  fails
@ 2019-10-09 11:59 99% Joakim Tjernlund
  0 siblings, 0 replies; 1+ results
From: Joakim Tjernlund @ 2019-10-09 11:59 UTC (permalink / raw
  To: gentoo-portage-dev@lists.gentoo.org

Trying to upgrade portage in an older embedded target I get:
When upgrading from old 2.3.62 
    >>> Merging sys-apps/portage-2.3.65 to /
    /usr/bin/python3.4: Error while finding spec for 'portage._compat_upgrade.default_locations' (<class 'ImportError'>: No module named 'portage._compat_upgrade')
     * ERROR: sys-apps/portage-2.3.65::tmv3-target-overlay failed (preinst phase):
     *   (no error message)
     *
     * Call stack:
     *     ebuild.sh, line 133:  Called pkg_preinst
     *   environment, line 3193:  Called die
     * The specific snippet of code:
     *       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;
     *

Not a python expert but isn't portage trying to use a new function in portage(portage._compat_upgrade.default_locations) before
it is installed?

How should I resolve this?


 Jocke

^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2019-10-09 11:59 99% [gentoo-portage-dev] Portage upgrade from 2.3.62 to 2.3.65 fails Joakim Tjernlund

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox