551950 – dev-python/pyxattr-0.5.5 USE=doc - no theme named 'classic' found

Bug 551950 - dev-python/pyxattr-0.5.5 USE=doc - no theme named 'classic' found

Summary: dev-python/pyxattr-0.5.5 USE=doc - no theme named 'classic' found

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Development (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Robin Johnson

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2015-06-13 08:31 UTC by Martin von Gagern
Modified:	2015-06-18 12:22 UTC (History)
CC List:	3 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Martin von Gagern 2015-06-13 08:31:21 UTC

sphinx-build -b html -d doc/doctrees -W doc doc/html
Making output directory...
Running Sphinx v1.2.2
loading pickled environment... not yet created

Theme error:
no theme named 'classic' found (missing theme.conf?)
Makefile:17: recipe for target 'doc/html/index.html' failed
make: *** [doc/html/index.html] Error 1
 * ERROR: dev-python/pyxattr-0.5.5::gentoo failed (compile phase):
 *   emake failed


This looks very similar to bug 549234, which suggests changing the sphinx dependency to >=dev-python/sphinx-1.3.1 which will provide a theme of that name. However, the way I read it, that package was actually using the 'default' theme until bug 548486 changed that to 'classic'. So one might also consider applying that sed line only if sphinx is recent enough to need it.

I'm at dev-python/sphinx-1.2.2, presumably due to sage-on-gentoo requirements, so I guess personally I'll simply disable docs for this package for now.

Comment 1 Justin Lecher (RETIRED) gentoo-dev

2015-06-16 08:21:23 UTC

+  16 Jun 2015; Justin Lecher <jlec@gentoo.org> pyxattr-0.5.3.ebuild,
+  pyxattr-0.5.5.ebuild, pyxattr-9999.ebuild:
+  Adjust sphinx version to support new theme names, bug #551950, bug #548486
+

Comment 2 Justin Lecher (RETIRED) gentoo-dev

2015-06-18 09:47:53 UTC

*** Bug 552352 has been marked as a duplicate of this bug. ***

Comment 3 Juergen Rose 2015-06-18 11:35:31 UTC

(In reply to Martin von Gagern from comment #0)

...
> I'm at dev-python/sphinx-1.2.2, presumably due to sage-on-gentoo
> requirements, so I guess personally I'll simply disable docs for this
> package for now.

How it is possible to disable docs for sage-on-gentoo?

Comment 4 Justin Lecher (RETIRED) gentoo-dev

2015-06-18 11:39:06 UTC

(In reply to Juergen Rose from comment #3)
> (In reply to Martin von Gagern from comment #0)
> 
> ...
> > I'm at dev-python/sphinx-1.2.2, presumably due to sage-on-gentoo
> > requirements, so I guess personally I'll simply disable docs for this
> > package for now.
> 
> How it is possible to disable docs for sage-on-gentoo?

Best is to ask on the mailing list.

Comment 5 Martin von Gagern 2015-06-18 11:40:59 UTC

(In reply to Juergen Rose from comment #3)
> How it is possible to disable docs for sage-on-gentoo?

I meant pyxattr.

Comment 6 Justin Lecher (RETIRED) gentoo-dev

2015-06-18 11:42:00 UTC

(In reply to Martin von Gagern from comment #5)
> (In reply to Juergen Rose from comment #3)
> > How it is possible to disable docs for sage-on-gentoo?
> 
> I meant pyxattr.

USE=-doc emerge -1 pyxattr

Comment 7 Juergen Rose 2015-06-18 12:22:12 UTC

(In reply to Justin Lecher from comment #6)
> (In reply to Martin von Gagern from comment #5)
> > (In reply to Juergen Rose from comment #3)
> > > How it is possible to disable docs for sage-on-gentoo?
> > 
> > I meant pyxattr.
> 
> USE=-doc emerge -1 pyxattr

This I know. But I want to disable docs for sage-on-gentoo, because I think, that sage-doc blocks sphinx-1.3.1.