Summary: | dev-python/xlwt-1.0.0 USE=doc should depend on >=dev-python/sphinx-1.3.1 - Theme error: no theme named 'classic' found (missing theme.conf?) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alunduil, Martin.vGagern |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://sphinx-doc.org/changes.html#release-1-3b3-released-feb-24-2015 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 549148 | ||
Attachments: | build.log |
Description
Juergen Rose
2015-05-12 06:06:11 UTC
Created attachment 403108 [details]
build.log
'USE=-doc emerge -v xlwt' works. Release 1.3b3 (released Feb 24, 2015) The ‘default’ html theme has been renamed to ‘classic’. Just to confirm the only action required to solve this issue is changing the dependency on sphinx to >=1.3.1, correct? If I get confirmation, I'll go ahead and fix this ebuild. Thanks in advance. From my observation, this would work, however what triggered this was the use of Running Sphinx v1.2.2, the stable version. But the need to have to keyword a package to ~ in a stable system is hardly new. The docs built fine since I had Installed versions: 1.3.1 Setting the border appears the most robust solution from other options. I've encountered this one here, and also the related bug #548486. The latter is due to the ebuild changing the theme name without bumping the sphinx dependency. Converely it should be possible here to detect an older version of sphinx, and change the theme to 'default'. (In reply to Juergen Rose from comment #0) > 'emerge xlwt' fails with: > ... > make -j9 -C docs html > make: Entering directory > '/var/tmp/portage/dev-python/xlwt-1.0.0/work/xlwt-1.0.0/docs' > sphinx-build -b html -d _build/doctrees . _build/html > Making output directory... > Running Sphinx v1.2.2 As a general remark, mixing arch and ~arch isn't supported. You will always run in such problems doing so. If you need packages being moved from ~arch to arch, file bugs please. (In reply to Justin Lecher from comment #7) > As a general remark, mixing arch and ~arch isn't supported. You will always > run in such problems doing so. If you need packages being moved from ~arch > to arch, file bugs please. It's in fact the oppsite way around for me: mostly ~arch with a few things kept at lower versions. I'm using sage from the sage overlay, which has some very specific version dependencies for some of the stuff it uses. E.g. sci-mathematics/sage-doc-6.7 depends on ~dev-python/sphinx-1.2.2 which prevents me from upgrading to the ~arch version even though I usually run ~arch for my system. 16 Jun 2015; Justin Lecher <jlec@gentoo.org> xlwt-1.0.0.ebuild: Rise version number of sphinx, bug #549234 |