| 1 |
It seems that every time a new Python version is unmasks, it breaks |
| 2 |
something on one or another of my machines. |
| 3 |
|
| 4 |
This time it's a python-exec version conflict that prevents emerge |
| 5 |
-u. FAICT, Python 3.10 requires python-exec 2.4.8, and some other |
| 6 |
package requires 2.4.6. |
| 7 |
|
| 8 |
I've fixed things temporarily with: |
| 9 |
|
| 10 |
package.use: |
| 11 |
|
| 12 |
*/* PYTHON_TARGETS: -python3_10 |
| 13 |
*/* PYTHON_SINGLE_TARGET -python3_10 |
| 14 |
|
| 15 |
package.mask: |
| 16 |
|
| 17 |
>=dev-lang/python-3.10 |
| 18 |
|
| 19 |
Now, at least I can continue to update the machine. |
| 20 |
|
| 21 |
When I get the spare time to try to get Python 3.10 working, what is |
| 22 |
the easiest way to figure out which package is causing the problem by |
| 23 |
requring the older version of python-exec? |
| 24 |
|
| 25 |
I've tried adding a 't' to the emerge flags, but that doesn't seem to |
| 26 |
show anything useful. |
| 27 |
|
| 28 |
Is there any documentation on how to determine the cause of a package |
| 29 |
version conflict? |
| 30 |
|
| 31 |
Here's what emerge says: |
| 32 |
|
| 33 |
(dev-lang/python-exec-conf-2.4.6:2/2::gentoo, ebuild scheduled for merge) pulled in by |
| 34 |
dev-lang/python-exec-conf required by (dev-lang/python-exec-2.4.8:2/2::gentoo, ebuild scheduled for merge) USE="(native-symlinks) -test" ABI_X86="(64)" PYTHON_TARGETS="(pypy3) (python3_10) (python3_8) (python3_9)" |
| 35 |
|
| 36 |
|
| 37 |
python-exec-2.4.8 requires python-exec-conf which requires python-exec 2.4.6? |
Archives