On 12/30/20 1:05 AM, Michael wrote:
On Tuesday, 29 December 2020 22:55:03 GMT Neil Bothwick wrote:
On Tue, 29 Dec 2020 23:16:11 +0100, n952162 wrote:
So, I tried to do an emerge on @system. I got another slot conflict!
This time for mako, which I'd seen go by sometimes as a "package of
interest". It's only transgression: PYTHON_TARGET containing
python3_7.
Note that both the "scheduled for merge" depender and the "installed"
depender both required the same version of mako, 1.1.1-r1. The only
difference is the fact that one requirements specification has
python3-7, the other python3-8. The same pkg, the same binaries.
Something is wrong here. Why is it not good enough to specify python3?
PYTHON_TARGET determines for which version(s) of Python a package
installs its modules. The modules may be identical, but 3.7 and 3.8 have
different search paths, e.g. /usr/lib/python3.7/site-packages vs.
/usr/lib/python3.8/site-packages.
It is possible you have some old python_targets settings in package.use,
that's where I would check first.
As discussed recently, removing any manually configured python targets and
letting portage work its magic, rather than fighting against it, is usually a
sound way to get out of such a muddle.
I sync'ed portage a few hours ago today. Neither mako, nor setuptools require
anything other than python3_8 on this system:
$ eix -l setuptools
[I] dev-python/setuptools
Available versions:
46.4.0-r3 ^t [test PYTHON_TARGETS="pypy3 python2_7
python3_6 python3_7 python3_8 python3_9"] ["|| ( python_targets_pypy3
python_targets_python2_7 python_targets_python3_6 python_targets_python3_7
python_targets_python3_8 python_targets_python3_9 )"]
50.3.0 ^t [test PYTHON_TARGETS="pypy3 python3_6
python3_7 python3_8 python3_9"] ["|| ( python_targets_pypy3
python_targets_python3_6 python_targets_python3_7 python_targets_python3_8
python_targets_python3_9 )"]
~ 51.0.0 ^t [test PYTHON_TARGETS="pypy3 python3_6
python3_7 python3_8 python3_9"] ["|| ( python_targets_pypy3
python_targets_python3_6 python_targets_python3_7 python_targets_python3_8
python_targets_python3_9 )"]
~ 51.1.0 ^t [test PYTHON_TARGETS="pypy3 python3_6
python3_7 python3_8 python3_9"] ["|| ( python_targets_pypy3
python_targets_python3_6 python_targets_python3_7 python_targets_python3_8
python_targets_python3_9 )"]
Installed versions: 50.3.0^t(12:47:38 05/12/20)(-test
PYTHON_TARGETS="python3_8 -pypy3 -python3_6 -python3_7 -python3_9")
Homepage: https://github.com/pypa/setuptools https://pypi.org/
project/setuptools/
Description: Collection of extensions to Distutils
$ eix -l mako
[I] dev-python/mako
Available versions:
1.1.3-r1 ^t [doc test PYTHON_TARGETS="pypy3 python3_6
python3_7 python3_8 python3_9"] ["|| ( python_targets_pypy3
python_targets_python3_6 python_targets_python3_7 python_targets_python3_8
python_targets_python3_9 )"]
Installed versions: 1.1.3-r1^t(13:09:34 05/12/20)(-doc -test
PYTHON_TARGETS="python3_8 -pypy3 -python3_6 -python3_7 -python3_9")
Homepage: https://www.makotemplates.org/ https://pypi.org/
project/Mako/
Description: A Python templating language
...
Well, yes, the current version, indeed requires python3_8. The version
that was installed on my system, however, to be updated, listed
python3_7 in the PYTHON_TARGETS section. That was the only difference
between the two packages in the collision. It apparently disqualified
the update with a slot conflict.
