| 1 |
Hi, |
| 2 |
|
| 3 |
I'd like to update a system that is about 1 year old. I have python3.7 |
| 4 |
and python 3.8 installed, 3.7 is the default. After updating the repo, |
| 5 |
it was suggested to update portage first (probably useful to support |
| 6 |
new EAPI versions). |
| 7 |
I read about updating to python 3.9, so I created |
| 8 |
|
| 9 |
--- |
| 10 |
~ # cat /etc/portage/package.use/py |
| 11 |
*/* PYTHON_TARGETS: -* python3_9 python3_8 |
| 12 |
*/* PYTHON_SINGLE_TARGET: -* python3_9 |
| 13 |
--- |
| 14 |
|
| 15 |
as suggested. However, there are still collisions (and I don't really |
| 16 |
understand them): |
| 17 |
|
| 18 |
--- |
| 19 |
~ # emerge -p --oneshot sys-apps/portage |
| 20 |
|
| 21 |
These are the packages that would be merged, in order: |
| 22 |
|
| 23 |
Calculating dependencies... done! |
| 24 |
[ebuild N ] acct-group/portage-0 |
| 25 |
[ebuild N ] acct-user/portage-0 |
| 26 |
[ebuild U ] sys-devel/automake-1.16.4 [1.16.1-r1] USE="-test%" |
| 27 |
[ebuild NS ] dev-lang/python-3.9.6_p2 [2.7.18-r2, 3.7.8-r2, 3.8.5] |
| 28 |
USE="sqlite* -verify-sig%" |
| 29 |
[ebuild U ] dev-python/certifi-10001-r1 [10001] |
| 30 |
PYTHON_TARGETS="python3_8* python3_9* (-python3_10)" |
| 31 |
[ebuild U ] dev-python/setuptools-57.4.0-r2 [46.4.0-r3] |
| 32 |
PYTHON_TARGETS="python3_8* python3_9* (-python3_10)" |
| 33 |
[ebuild N ] dev-python/toml-0.10.2 USE="-test" |
| 34 |
PYTHON_TARGETS="python3_8 python3_9 (-pypy3) (-python3_10)" |
| 35 |
[ebuild U ] dev-python/setuptools_scm-6.0.1-r1 [4.1.2-r1] |
| 36 |
PYTHON_TARGETS="python3_8* python3_9* (-python3_10)" |
| 37 |
[ebuild N ] dev-python/charset_normalizer-2.0.4 USE="-test" |
| 38 |
PYTHON_TARGETS="python3_8 python3_9 (-pypy3) (-python3_10)" |
| 39 |
[ebuild U ] dev-python/idna-3.2 [2.10-r1] PYTHON_TARGETS="python3_8* |
| 40 |
python3_9* (-python3_10)" |
| 41 |
[ebuild R ] dev-python/PySocks-1.7.1-r1 PYTHON_TARGETS="python3_8* |
| 42 |
python3_9* (-python3_10)" |
| 43 |
[ebuild U ] dev-python/urllib3-1.26.6 |
| 44 |
[1.25.10-r1] PYTHON_TARGETS="python3_8* python3_9* (-python3_10)" |
| 45 |
[ebuild U ] dev-python/requests-2.26.0 [2.24.0-r1] |
| 46 |
PYTHON_TARGETS="python3_8* python3_9* (-python3_10)" |
| 47 |
[ebuild U ] app-portage/gemato-16.2 [15.2] |
| 48 |
PYTHON_TARGETS="python3_8* python3_9* (-python3_10)" |
| 49 |
[ebuild U ] sys-apps/portage-3.0.20-r6 [3.0.4-r1] |
| 50 |
PYTHON_TARGETS="python3_8* python3_9* (-python3_10)" |
| 51 |
|
| 52 |
!!! Multiple package instances within a single package slot have been |
| 53 |
pulled !!! into the dependency graph, resulting in a slot conflict: |
| 54 |
|
| 55 |
sys-apps/portage:0 |
| 56 |
|
| 57 |
(sys-apps/portage-3.0.20-r6:0/0::gentoo, ebuild scheduled for merge) |
| 58 |
USE="(ipc) native-extensions rsync-verify xattr -apidoc -build -doc |
| 59 |
-gentoo-dev (-selinux) -test" ABI_X86="(64)" |
| 60 |
PYTHON_TARGETS="python3_8 python3_9 (-pypy3) (-python3_10)" pulled in |
| 61 |
by sys-apps/portage (Argument) |
| 62 |
|
| 63 |
(sys-apps/portage-3.0.4-r1-3:0/0::gentoo, installed) USE="(ipc) |
| 64 |
native-extensions rsync-verify xattr -apidoc -build -doc -gentoo-dev |
| 65 |
(-selinux) -test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) |
| 66 |
-python3_6 -python3_8 -python3_9" pulled in by |
| 67 |
sys-apps/portage[python_targets_python3_7(-),-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-)] |
| 68 |
required by (app-portage/gentoolkit-0.5.0:0/0::gentoo, installed) |
| 69 |
USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) |
| 70 |
-python3_6 -python3_8" |
| 71 |
|
| 72 |
[...] |
| 73 |
--- |
| 74 |
|
| 75 |
|
| 76 |
|
| 77 |
Plus many similar ones on packages like setuptools, gemato etc. |
| 78 |
I don't see how to get out of this vicious circle, any hints? |
| 79 |
|
| 80 |
|
| 81 |
cu |
| 82 |
Gerrit |
Archives