| Summary: | dev-python/sphinx-bootstrap-theme-0.4.0 - ImportError: No module named 'setuptools' | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Andrey Grozin <grozin> |
| Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build log | ||
|
Description
Andrey Grozin
2014-09-19 08:17:40 UTC
I see. setuptools has not been emerged for python-3.3. But I cannot emerge it in any way except as a member of a list of about 100 packages. And portage, for some reason, decided to emerge this sphinx-bootstrap-theme before setuptools.
elrond ~ # emerge -av1 setuptools
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] dev-python/setuptools-5.7 USE="{-test}" PYTHON_TARGETS="python2_7 python3_3* python3_4* -pypy (-python3_2*)" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-python/setuptools:0
(dev-python/setuptools-5.7:0/0::gentoo, ebuild scheduled for merge) pulled in by
dev-python/setuptools (Argument)
(dev-python/setuptools-5.7:0/0::gentoo, installed) pulled in by
dev-python/setuptools[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-)] required by (dev-python/numpy-1.8.2:0/0::gentoo, installed)
dev-python/setuptools[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_pypy(-)] required by (dev-python/pytz-2014.7:0/0::gentoo, installed)
dev-python/setuptools[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_pypy(-)] required by (dev-python/pygments-1.6_p20140324:0/0::gentoo, installed)
dev-python/setuptools[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-)] required by (dev-python/pyflakes-0.8.1:0/0::gentoo, installed)
dev-python/setuptools[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_pypy(-)] required by (dev-python/cssutils-0.9.10-r1:0/0::gentoo, installed)
dev-python/setuptools[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_pypy(-)] required by (dev-python/sphinx-1.2.2:0/0::gentoo, installed)
dev-python/setuptools[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_pypy(-)] required by (dev-python/chardet-2.2.1:0/0::gentoo, installed)
dev-python/setuptools[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,python_targets_pypy(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-),-python_single_target_pypy(-)] required by (dev-python/logilab-common-0.61.0:0/0::gentoo, installed)
dev-python/setuptools[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,python_targets_python3_4(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-),-python_single_target_python3_4(-)] required by (dev-python/ipython-1.2.1:0/0::gentoo, installed)
dev-python/setuptools[python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-)] required by (sci-libs/gdal-1.10.1:0/0::gentoo, installed)
It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.
For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.
Actually the list of packages which portage accepts (without these "multiple instances in a slot") is not 100 but 167 packages long. But portage tries to emerge them in such an order that the whole thing fails. What next? How can I get something usable after excluding python3_2 from PYTHON_TARGETS? makes this appear a side effect of trying to purge py3.2 from your PYTHON_TARGETS while py3.2 is still being pulled in as an active python impl. afaik the py3.2 use flags is masked but py3.2 isn't and why this is so is in the hands of that dev managing its demise. I'd predict further down the track this kind of grief will disappear once py3.2 as an impl is (finally) masked and this block will disappear and this bug can be closed obsolete or can'tfix OK, I've found a workaround. It is long and tedious, but it works. After changing PYTHON_TARGETS="python2_7 python3_2" to "python2_7 python3_3 python3_4" 1. eselect python-3.2 (I already have all packages emerged for 3.2) 2. set USE=-doc (otherwise portage will try to emerge sphinx-bootstrap-theme early and will fail) 3. emerge a long list of packages (start from trying setuptools and add everything mentioned in portage error messages; the process terminates after 10 iterations or slightly more, and includes non-python packages like sci-libs/gdal or kde-base/kate) 4. eselect python-3.3 5. set USE=doc (I always have it this way) 6. Re-emerge the same list of packages (some additional ones will be pulled in by USE=doc) |