In my embedded target I tried to upgrade portage and got this: ebuild /usr/local/portage/tmv3-target-overlay/sys-apps/portage/portage-2.3.65.ebuild qmerge >>> Existing ${T}/environment for 'portage-2.3.65' will be sourced. Run >>> 'clean' to start with a fresh environment. * Removing /usr/share/man/* * Removing /usr/share/doc/* * Removing /usr/share/man * Removing /usr/share/doc * checking 3886 files for package collisions 1000 files checked ... 2000 files checked ... 3000 files checked ... >>> 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; * * If you need support, post the output of `emerge --info '=sys-apps/portage-2.3.65::tmv3-target-overlay'`, * the complete build log and the output of `emerge -pqv '=sys-apps/portage-2.3.65::tmv3-target-overlay'`. * The complete build log is located at '/var/tmp/portage/sys-apps/portage-2.3.65/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/portage-2.3.65/temp/environment'. * Working directory: '/var/tmp/portage/._portage_reinstall_.6c_8_0zh/pym' * S: '/var/tmp/portage/sys-apps/portage-2.3.65/work/portage-2.3.65' !!! FAILED preinst: 1
It is sad to read that you have problems to upgrade portage. The situation seems to be a bit more complicate and requires some analysis. We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3]. I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4]. Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://forums.gentoo.org/ [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html [4] https://www.gentoo.org/support/
(In reply to Jonas Stein from comment #1) > It is sad to read that you have problems to upgrade portage. The situation > seems to be a bit more complicate and requires some analysis. > We can not help you efficiently via bug tracker. The bug tracker aims rather > on specific problems in .ebuilds and less on individual systems. > > I have had very good experience on the gentoo IRC [1] with questions like > this. Of course there are also forums and mailing lists [2,3]. > I hope you understand, that I will close the bug here therefore and wish you > good luck on one of the mentioned channels [4]. > Please reopen the ticket in order to provide an indication for an specific > error in an ebuild or any gentoo related product. > > [1] https://www.gentoo.org/get-involved/irc-channels/ > [2] https://forums.gentoo.org/ > [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html > [4] https://www.gentoo.org/support/ To me this appears to be a compatibility problem for an older portage to upgrade itself, something I presumed always should work. Would be nice if you would allow the portage team to comment on that.
