| 1 |
On Tue, 29 Dec 2020 23:16:11 +0100, n952162 wrote: |
| 2 |
|
| 3 |
> > So, I tried to do an emerge on @system. I got another slot conflict! |
| 4 |
> > This time for mako, which I'd seen go by sometimes as a "package of |
| 5 |
> > interest". It's only transgression: PYTHON_TARGET containing |
| 6 |
> > python3_7. |
| 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 |
|
| 14 |
PYTHON_TARGET determines for which version(s) of Python a package |
| 15 |
installs its modules. The modules may be identical, but 3.7 and 3.8 have |
| 16 |
different search paths, e.g. /usr/lib/python3.7/site-packages vs. |
| 17 |
/usr/lib/python3.8/site-packages. |
| 18 |
|
| 19 |
It is possible you have some old python_targets settings in package.use, |
| 20 |
that's where I would check first. |
| 21 |
|
| 22 |
|
| 23 |
-- |
| 24 |
Neil Bothwick |
| 25 |
|
| 26 |
Growing old is mandatory; growing up is optional!! |
Archives