Re: [gentoo-user] override PYTHON_TARGETS to avoid a slot collision

[Arve Barsnes]

On Wed, 16 Dec 2020 at 11:34, Miles Malone
<m.malone@××××××××××××××××××.net> 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.

> > If the package was good enough before, it's likely still good enough.  Where's the problem?  I've (unsuccessfully) made these attempts:
> >
> > # */* PYTHON_TARGETS: python3_6 python3_7 python3_8 python3_9
> > #*/* PYTHON_TARGETS: -python3_6 -python3_7 python3_8 python3_9
> > # just have one set
> > */* PYTHON_TARGETS: python3_8

Is there any reason that you need to add py3.9 to all packages? If you
need it for something special, add it to those packages only, and let
portage take care of python targets for you instead of continuously
trying these big hammers. Ideally you should have *no* python targets
set manually in make.conf or USE files.

> > The emerge command was:
> >
> > sudo emerge --verbose=y -vuUD   --verbose-conflicts   dev-python/setuptools dev-python/setuptools_scm dev-python/certifi dev-python/markupsafe dev-python/jinja dev-libs/libxml2

Since it seems sphinx is installed with a different set of python
targets than what you're trying to update, you should include sphinx
in that emerge command to let it update to the same python targets and
solve the conflict.

Regards,
Arve