Bug 1714806 - FTBFS: python-mongoengine
Summary: FTBFS: python-mongoengine
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-mongoengine
Version: rawhide
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Randy Barlow
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F31FTBFS PYTHON38 1732841
TreeView+ depends on / blocked
 
Reported: 2019-05-28 22:41 UTC by Randy Barlow
Modified: 2019-07-31 22:40 UTC (History)
3 users (show)

Fixed In Version: python-mongoengine-0.15.3-4.fc31
Clone Of:
Environment:
Last Closed: 2019-05-28 22:57:56 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Randy Barlow 2019-05-28 22:41:10 UTC 
Description of problem:
python-mongoengine is failing to build from source against Python 3.8[0]. It seems to be due to sphinx_rtd_theme missing:

+ PYTHONPATH=/builddir/build/BUILD/mongoengine-0.15.3
+ make -C docs SPHINXBUILD=sphinx-build-3 html
make: Entering directory '/builddir/build/BUILD/mongoengine-0.15.3/docs'
sphinx-build-3 -b html -d _build/doctrees   . _build/html
Running Sphinx v2.0.1
BUILDSTDERR: Configuration error:
BUILDSTDERR: There is a programmable error in your configuration file:
BUILDSTDERR: Traceback (most recent call last):
BUILDSTDERR:   File "/usr/lib/python3.8/site-packages/sphinx/config.py", line 361, in eval_config_file
BUILDSTDERR:     execfile_(filename, namespace)
BUILDSTDERR:   File "/usr/lib/python3.8/site-packages/sphinx/util/pycompat.py", line 86, in execfile_
BUILDSTDERR:     exec(code, _globals)
BUILDSTDERR:   File "/builddir/build/BUILD/mongoengine-0.15.3/docs/conf.py", line 16, in <module>
BUILDSTDERR:     import sphinx_rtd_theme
BUILDSTDERR: ModuleNotFoundError: No module named 'sphinx_rtd_theme'


Additional info:
[0] https://copr-be.cloud.fedoraproject.org/results/@python/python3.8/fedora-rawhide-x86_64/00912219-python-mongoengine/build.log.gz
Comment 1 Randy Barlow 2019-05-28 22:48:42 UTC 
This also fails on Rawhide with Python 3.7.
Note You need to log in before you can comment on or make changes to this bug.