| 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 |
|
| 25 |
I don't understand what manually configured python targets are. There |
| 26 |
are, in general, no python specifiers on my system in |
| 27 |
/etc/portage/package.use or make.conf. Do you mean somewhere else? |
Archives