On 2019-12-19, Thomas Schweikle wrote: >>> > On 2019-12-18, <nunojsi...@ist.utl.pt> (Nuno Silva) < >>> > nunojsi...@ist.utl.pt> wrote: >>> > >>> > > The EAPI problem is in a package that is pulled as a dependency of >>> > > portage. >>> > > >>> > > Unless there's a simple hack to solve this, you will need to use older >>> > > ebuilds or split the update in several steps, using older versions of >>> > > the portage tree. The following notes show a way of achieving this: >>> > > >>> > > https://wiki.gentoo.org/wiki/User:NeddySeagoon/HOWTO_Update_Old_Gentoo [...] > So I've tried now to upgrade in various ways: > 1. the one given in https://anongit.gentoo.org/git/repo/sync/gentoo.git > But this fails as soon as I try to emerge git. python-exec is at version > 2.4.6 now. Without any 2.0.1 packed, legal versions left. Same for all > other dependencies. Not really a way to go ...
Looking at this again, the installed version of portage says (in the output quoted in your initial post) that it supports EAPI 6, which is also used by the python-exec-2.4.6 ebuild (not in the tree anymore, the one using EAPI 7 is 2.4.6-r1). So you could give the 2.4.6 ebuild a try: https://gitweb.gentoo.org/repo/gentoo.git/plain/dev-lang/python-exec/python-exec-2.4.6.ebuild?id=20664dd65ec565233f460b94efc0337249b84550 Hopefully this will allow you to upgrade portage, unless there are more dependencies of portage in similar situations. If this ebuild is not enough, any chance you have another machine where you could do the date-based checkout and then copy the entire portage tree? -- Nuno Silva
