| 1 |
n952162 wrote: |
| 2 |
> On 12/29/20 11:07 PM, n952162 wrote: |
| 3 |
>> |
| 4 |
>> |
| 5 |
>> So, I tried to do an emerge on @system. I got another slot conflict! |
| 6 |
>> This time for mako, which I'd seen go by sometimes as a "package of |
| 7 |
>> interest". It's only transgression: PYTHON_TARGET containing python3_7. |
| 8 |
>> |
| 9 |
>> |
| 10 |
> |
| 11 |
> Note that both the "scheduled for merge" depender and the "installed" |
| 12 |
> depender both required the same version of mako, 1.1.1-r1. The only |
| 13 |
> difference is the fact that one requirements specification has |
| 14 |
> python3-7, the other python3-8. The same pkg, the same binaries. |
| 15 |
> Something is wrong here. Why is it not good enough to specify python3? |
| 16 |
> |
| 17 |
> |
| 18 |
> |
| 19 |
> |
| 20 |
|
| 21 |
|
| 22 |
All I can say is there is a reason for it. It seems there is |
| 23 |
significant changes between 3.7, 3.8 and 3.9 that causes compatibility |
| 24 |
issues, which is why each is slotted I guess. There is a comment on |
| 25 |
this bug that may explain it better. |
| 26 |
|
| 27 |
https://bugs.gentoo.org/762406#c1 |
| 28 |
|
| 29 |
It should go to the comment but if it doesn't, it's the first actual |
| 30 |
comment by Michał Górny. There's also a thread on -dev about this but |
| 31 |
it is short and likely won't explain much. |
| 32 |
|
| 33 |
Dale |
| 34 |
|
| 35 |
:-) :-) |
Archives