On 2021.12.22 17:31, Steven Lembark wrote:
On Tue, 21 Dec 2021 20:21:17 -0500
Jack <ostrof...@users.sourceforge.net> wrote:
> I may well be wront, but it looks like the problems are not due to
> version, but to python-target mismatches. You may need to rebuild
> some stuff first, such as pytest-runner and mako.
You are probably right: I've spent more time playing with
PYTHON*TARGET variables and succesive rebuilds on this machine
than actually doing any work for about a year. Annoyance is
that I don't do anything else with Python here so it's only
for the package manager.
This is for a fresh build from a recent stage3. It shouldn't
be this painful to just start a new system.
With a new system, I would think you should not need to alter the
profile defaults in any way. Once you do anything manually to those
python variables, it likely devolves into a black hole.
I would find any python-target related variables in any portage config
files, and seriously consider removing them.
As someone recently suggested in a different thread, start with just
"emerge @system" then "emerge @world" (without any non-default options)
and only when that is done, start adding back the --newuse and --deep
options.
The other replies have also been good - in terms of where to start
looking. Also - which versions of python do you have installed, and
which do you actually need?
