| 1 |
On 2022.01.11 19:11, Grant Edwards wrote: |
| 2 |
> |
| 3 |
> It seems that every time a new Python version is unmasks, it breaks |
| 4 |
> something on one or another of my machines. |
| 5 |
> |
| 6 |
> This time it's a python-exec version conflict that prevents emerge |
| 7 |
> -u. FAICT, Python 3.10 requires python-exec 2.4.8, and some other |
| 8 |
> package requires 2.4.6. |
| 9 |
> |
| 10 |
> I've fixed things temporarily with: |
| 11 |
> |
| 12 |
> package.use: |
| 13 |
> |
| 14 |
> */* PYTHON_TARGETS: -python3_10 |
| 15 |
> */* PYTHON_SINGLE_TARGET -python3_10 |
| 16 |
> |
| 17 |
> package.mask: |
| 18 |
> |
| 19 |
> >=dev-lang/python-3.10 |
| 20 |
> |
| 21 |
> Now, at least I can continue to update the machine. |
| 22 |
> |
| 23 |
> When I get the spare time to try to get Python 3.10 working, what is |
| 24 |
> the easiest way to figure out which package is causing the problem by |
| 25 |
> requring the older version of python-exec? |
| 26 |
> |
| 27 |
> I've tried adding a 't' to the emerge flags, but that doesn't seem to |
| 28 |
> show anything useful. |
| 29 |
> |
| 30 |
> Is there any documentation on how to determine the cause of a package |
| 31 |
> version conflict? |
| 32 |
> |
| 33 |
> Here's what emerge says: |
| 34 |
> |
| 35 |
> (dev-lang/python-exec-conf-2.4.6:2/2::gentoo, ebuild scheduled for |
| 36 |
> merge) pulled in by |
| 37 |
> dev-lang/python-exec-conf required by |
| 38 |
> (dev-lang/python-exec-2.4.8:2/2::gentoo, ebuild scheduled for merge) |
| 39 |
> USE="(native-symlinks) -test" ABI_X86="(64)" PYTHON_TARGETS="(pypy3) |
| 40 |
> (python3_10) (python3_8) (python3_9)" |
| 41 |
> |
| 42 |
> |
| 43 |
> python-exec-2.4.8 requires python-exec-conf which requires |
| 44 |
> python-exec 2.4.6? |
| 45 |
I was going to wonder if you are caught in the middle of an upgrade |
| 46 |
that's only partly reached the mirrors. Given that (as I see it, |
| 47 |
having last done a sync a few hours ago) that there is ONLY one version |
| 48 |
each in the tree for python-exec-2.4.8 and python-exec-conf-2.4.6. My |
| 49 |
response would just be wait an hour and re-sync. |
| 50 |
|
| 51 |
However, looking at the ebuilds: |
| 52 |
python-exe requires python-exec-conf (no version specified) |
| 53 |
python-exec-conf-2.4.6 requires "!<dev-lang/python-exec-2.4.6-r4" which |
| 54 |
should allow 2.4.8. |
| 55 |
|
| 56 |
I have both python 3.9.9-r1 and 3.10.0_p1-r1 installed (plus |
| 57 |
2.7.18_p13) so there doesn't seem to be any conflict there. What does |
| 58 |
"equery d python-exec" tell you? |
Archives