On 19/12/20 6:20 pm, n952162 wrote: > On 12/16/20 11:59 AM, Arve Barsnes wrote: >> On Wed, 16 Dec 2020 at 11:34, Miles Malone >> <[email protected]> wrote: >>> What's happening when you do emerge -avuDN --with-bdeps=y >>> --backtrack=100 @world ? Giving portage the flexibility to solve it >>> with some extra backtracking and increasing the scope to world might >>> fix it, if not then we can revisit it? >> You should definitely try this first if you haven't. > > > I have. > > ...
Backtracking rarely helps in my experience. check the blocks: using --nodeps forces the install, then it may work (you may have to add to package.accept_keywords etc. to cover that angle - but I am on arm and arm64 where the most difficult of the python problems happened for me) I also have: USE_PYTHON="3.8" PYTHON_TARGETS="python3_8" PYTHON_SINGLE_TARGET="python3_8" *** a number of packages from overlays I am using don't like 3.9 so I removed it) I have a number of intel, arm and arm64 and virtualised systems and all have problems with python in some way or other - I could only remove the python targets on a couple of them. After a mass update, I have been trying to remove the targets but its only working for a few so far, and they are not stable. I wish python would just go away and perl gets brought back - a lot less drama ... BillK
