I'm trying to avoid things depending on Python 2.7 and make them depend on Python 3.5 instead. I took portage-2.2.26.ebuild from gx86 portage tree and it works out of the box. Maybe time to bump the version now? Reproducible: Always
It's not that simple, I'm afraid. However, you can try my experimental backport of 2.2.26 into prefix-portage here: https://github.com/gmt/portage/tree/prefix-backporting-experimental Probably the easiest way to try it is to copy my ebuild from here: https://github.com/gmt/gmt-heroxbd-rap-overlay/tree/experimental/sys-apps/portage along with the rest of the tree into your overlay. They are based on a rebase of the prefix-portage ebuild against the mainline portage ebuild. Using this ebuild will probably result in a few extra dependencies. So long as you are using ~linux-x86 or ~linux-amd64, (maybe others -- haven't tested many ARCH's yet) all of those dependencies should be available in the same "experimental" branch of the above overlay. Not sure what would be the minimum dependencies. Watch out though: the ebuilds referenced in: https://github.com/gmt/gmt-heroxbd-rap-overlay/blob/experimental/profiles/features/rap/package.mask Have not been tested, you might want to NOT deploy those to your overlay, or otherwise, to duplicate those package.mask entries in your ${EPREFIX}/etc/portage/profile/package.mask.
It's fixed as of now. The latest version in prefix portage tree is 2.2.28-r4
