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

[n952162]

On 12/19/20 11:56 AM, Arve Barsnes wrote:
> On Sat, 19 Dec 2020 at 11:19, n952162 <n952162@×××.de> wrote:
>> I don't think this output or any list participant has actually identified where the problem here is.  In my original posting, the only difference causing the slot collision for jinja was that one had a PYTHON_TARGETS of 3-7 and the other of 3-8.  I asked how to force it to the correct value, but if someone explained that to me, I didn't understand it.
>
> Your output gives away that you STILL have not run depclean, so you
> STILL have dev-python/ipaddress installed, which has been removed from
> the tree, and requires python 2.7. Unless you remove old broken
> software you will NEVER get through a world update.


depclean output attached.

 >>> No packages selected for removal by depclean
Packages installed:   899
Packages in world:    291
Packages in system:   43
Required packages:    899
Number removed:       0

The one run on the previous day, a week ago today, had 314144 lines.


>
> Also: don't set PYTHON_TARGETS unless you have a REALLY good reason.
> You can set it on a specific package (and preferrable to set it only
> on a specific version of that package) to go around problems, but
> DON'T do this until you have made your system sane (meaning you can
> run world updates without troubles).
>

In the original posting of this thread, I presented a slot collision
where the only difference between the two packages was the
PYTHON_TARGET.  I interpret that to mean that new dependencies want the
new python.  Since the package is the same, it ought to be possible to
tell emerge(1) to assume a specific PYTHON_TARGET. Otherwise, there's no
way out of the dilemma.  If setting the PYTHON_TARGET as I've done it is
not effective, do you know another way?