The update of openvswitch from v2.6.1 to v2.7.0 fails while making the htmldocs: Warning, treated as error: WARNING: 'default' html theme has been renamed to 'classic'. Please change your html_theme setting either to the new 'alabaster' default theme, or to 'classic' to keep using the old default. make[2]: *** [Makefile:6161: htmldocs] Error 1 make[2]: *** Waiting for unfinished jobs.... Reproducible: Always Steps to Reproduce: 1. emerge -uDN world 2. 3. Actual Results: Warning, treated as error: WARNING: 'default' html theme has been renamed to 'classic'. Please change your html_theme setting either to the new 'alabaster' default theme, or to 'classic' to keep using the old default. make[2]: *** [Makefile:6161: htmldocs] Error 1 make[2]: *** Waiting for unfinished jobs.... Expected Results: Normally the emerge should have completed successfully. I see the following interesting code fragments in /var/tmp/portage/net-misc/openvswitch-2.7.0/work/openvswitch-2.7.0/Documentation/conf.py try: import ovs_sphinx_theme use_ovs_theme = True except ImportError: print("Cannot find 'ovs_sphinx' package. Falling back to default theme.") use_ovs_theme = False . . . if use_ovs_theme: html_theme = 'ovs' else: html_theme = 'default' I do not have sphinx installed: equery list -p dev-python/sphinx * Searching for sphinx in dev-python ... [-P-] [ ] dev-python/sphinx-1.1.3-r8:0 [-P-] [ ] dev-python/sphinx-1.2.2-r1:0 [-P-] [ ~] dev-python/sphinx-1.2.3-r1:0 [-P-] [ ] dev-python/sphinx-1.3.1-r2:0 [-P-] [ ~] dev-python/sphinx-1.3.5-r1:0 [-P-] [ ~] dev-python/sphinx-1.5.1-r2:0 [-P-] [ ~] dev-python/sphinx-1.5.2:0 I tried to emerge both with and without the use flag 'monitor'. The results were the same.
Today I looked into the matter some more. I decided to edit the file /var/tmp/portage/net-misc/openvswitch-2.7.0/work/openvswitch-2.7.0/Documentation/conf.py and change the default_theme assignment into 'classic'. After that I recomiled using the command 'ebuild /usr/portage/net-misc/openvswitch/openvswitch-2.7.0.ebuild compile', which now ran to completion successfully. I then installed the package using the ebuild tool. So the problem is the default setting of the sphinx theme for the documentation. Please note that I do not have the ovs theme installed on my system. I hope this helps you fixing the problem in the next release of the ebuild.
Are you using -Werror?
No, I didn't fiddle with any gcc arguments. I'm just emerging the openvswitch package. The only thing I patched was changing html_theme = 'default' into html_theme = 'classic', as I already described. The use flags I use are: # equery uses openvswitch [ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for net-misc/openvswitch-2.7.0: U I - - debug : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces - - modules : Build the kernel modules + + monitor : Build the Python and GUI dependent monitor applications + + python_targets_python2_7 : Build with Python 2.7 + + python_targets_python3_4 : Build with Python 3.4 + + ssl : Add support for Secure Socket Layer connections
I've sent a patch upstream, but it doesn't look to be going well (at least as a simple one liner). Here's the current questions. https://mail.openvswitch.org/pipermail/ovs-dev/2017-April/330982.html
Yeah, I understand. The funny thing is that according to Portage I don't have sphinx installed. (see the output of equery below) However, if I type 'sphinx in bash and hit autocompletion, bash comes up with: werkstation ~ # sphinx- sphinx-apidoc sphinx-autogen sphinx-build sphinx-quickstart Equery output: # equery list -p sphinx * Searching for sphinx ... !!! Ambiguous package name. Choose from: app-misc/sphinx dev-python/sphinx # equery list -p dev-python/sphinx * Searching for sphinx in dev-python ... [-P-] [ ] dev-python/sphinx-1.1.3-r8:0 [-P-] [ ] dev-python/sphinx-1.2.2-r1:0 [-P-] [ ~] dev-python/sphinx-1.2.3-r1:0 [-P-] [ ] dev-python/sphinx-1.3.1-r2:0 [-P-] [ ~] dev-python/sphinx-1.3.5-r1:0 [-P-] [ ~] dev-python/sphinx-1.5.1-r2:0 [-P-] [ ~] dev-python/sphinx-1.5.2:0 # equery list -p app-misc/sphinx * Searching for sphinx in app-misc ... [-P-] [ ] app-misc/sphinx-0.9.9:0 [-P-] [ ] app-misc/sphinx-2.0.10:0 [-P-] [ ] app-misc/sphinx-2.1.9:0 [-P-] [ ] app-misc/sphinx-2.2.11:0
# equery belongs `which sphinx-autogen` * Searching for /usr/bin/sphinx-autogen ... dev-python/sphinx-1.3.1-r1 (/usr/bin/sphinx-autogen -> ../lib/python-exec/python-exec2)
Upstream has this patch, works with old and new sphinx. https://mail.openvswitch.org/pipermail/ovs-dev/2017-April/331014.html fixed in 2.7.0-r2
