| Summary: | sys-apps/portage-2.3.42-r1: weird suggestion for dep-cycle involving nose/twisted/zope-* | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Michał Górny <mgorny> |
| Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | setuptools.txt | ||
The +python_targets_pypy3 solution must come from these conditional deps that omit python_targets_pypy3 in the nose-1.3.7-r3 ebuild, since some python targets have to be enabled in order to satisfy REQUIRED_USE:
> test? ( || ( $(python_gen_cond_dep 'dev-python/twisted[${PYTHON_USEDEP}]' python2_7 python3_{4,5,6})
> $(python_gen_cond_dep 'dev-python/twisted-core[${PYTHON_USEDEP}]' python2_7)
> ) )"
Something like this in the nose-1.3.7-r3 ebuild would suppress the issue: REQUIRED_USE="test? ( !python_targets_pypy !python_targets_pypy3 )" |
Created attachment 539514 [details] setuptools.txt * Error: circular dependencies: (dev-python/zope-interface-4.5.0:0/0::gentoo, ebuild scheduled for merge) depends on (dev-python/zope-event-4.3.0:0/0::gentoo, ebuild scheduled for merge) (buildtime) (dev-python/nose-1.3.7-r3:0/0::gentoo, ebuild scheduled for merge) (buildtime) (dev-python/twisted-18.4.0:0/0::gentoo, ebuild scheduled for merge) (buildtime) (dev-python/zope-interface-4.5.0:0/0::gentoo, ebuild scheduled for merge) (runtime) It might be possible to break this cycle by applying any of the following changes: - dev-python/zope-interface-4.5.0 (Change USE: -test) - dev-python/zope-event-4.3.0 (Change USE: -test) - dev-python/nose-1.3.7-r3 (Change USE: -python_targets_python2_7 +python_targets_pypy -python_targets_python3_5) (This change might require USE changes on parent packages.)- dev-python/nose-1.3.7-r3 (Change USE: -test) - dev-python/nose-1.3.7-r3 (Change USE: +python_targets_pypy3 -python_targets_python2_7 -python_targets_python3_5) (This change might require USE changes on parent packages.) Note that this change can be reverted, once the package has been installed. The first two suggestions seem to make sense but I have no clue why it thinks enabling pypy* would help. FTR, this system doesn't have pypy enabled anywhere and it never had. It's a relatively clean stage3 where I enabled FEATURES=test, python3_7 (done 'gpy-upgrade-impl -f 3.6 3.7' to get it into packages) and I'm trying to get initial 'emerge -1v setuptools' working. I've so far disabled FEATURES=test for the following packages in order to resolve dep loops: dev-python/linecache2 notest dev-python/pluggy notest dev-python/pytest notest dev-python/testtools notest dev-python/pbr notest dev-python/coverage notest dev-python/constantly notest dev-python/attrs notest dev-python/setuptools_scm notest dev-python/py notest I'm attaching the complete output. Lemme know what else would be helpful.