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