-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
While this wouldn't normally happen.. in the absense of {{dev-python/packaging}} and {{dev-python/wheel}} installed on a system, neither can be installed
It seems that there are hard changes in the upstream projects.
Find this new cycle:
Step 13/16 : RUN eval 'mkdir -p /var/cache/portage/distfiles || true' && chown portage:portage -R /var/cache/portage/ && USE="-python_targets_python2_7 -python_targets_python3_10 -python_targets_python3_7 -python_targets_python3_8 python_targets_python3_9" emerge dev-python/packaging -pv -t ---> Running in 96c3fc22d862 These are the packages that would be merged, in reverse order: Calculating dependencies ... done! [91m [0m[nomerge ] dev-python/packaging-21.3::python-modules-kit PYTHON_TARGETS="python3_9 -python2_7 -python3_10 -python3_7 -python3_8" [ebuild N ] dev-python/wheel-0.41.3::python-modules-kit PYTHON_TARGETS="python3_9 -pypy3 -python2_7 -python3_10 -python3_7 -python3_8" 97 KiB [ebuild N ] dev-python/packaging-21.3::python-modules-kit PYTHON_TARGETS="python3_9 -python2_7 -python3_10 -python3_7 -python3_8" 83 KiB Total: 2 packages (2 new), Size of downloads: 180 KiB [91m * Error: circular dependencies: (dev-python/wheel-0.41.3:0/0::python-modules-kit, ebuild scheduled for merge) depends on (dev-python/packaging-21.3:0/0::python-modules-kit, ebuild scheduled for merge) (runtime) (dev-python/wheel-0.41.3:0/0::python-modules-kit, ebuild scheduled for merge) (buildtime) * Note that circular dependencies can often be avoided by temporarily * disabling USE flags that trigger optional dependencies.
FWIS also in this case there are changes on build deps.
Version 21.3 of packaging requires wheel but the new tags use flit_core. I'm not sure if could be a valid solution to upgrade the version of packaging to fix this issue because I don't know the impacts.
