-
Notifications
You must be signed in to change notification settings - Fork 509
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs aren't building due to sphinx / jinja2 error #1613
Labels
Comments
Huh, I'm not sure why _static was configured like that either. Maybe it was part of the original auto-generated file? Or maybe we were using it before things got rearranged? Go ahead and make a pull request removing _static and changing Sphinx to 4.0.2 and we should be good to close this bug, then. Thank you for investigating! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like we got hit with an issue in sphinx / jinja2
sphinx-doc/sphinx#10291
We're currently pinned to an older version of Sphinx. Pinning versions is explicitly recommended by ReadTheDocs to improve the stability of their builds, so we'll still want to pin something that we know works:
/~https://github.com/intel/cve-bin-tool/blob/main/doc/requirements.txt
Recommended solution is to upgrade to Sphinx 4.0.2, temporary work around seems to be to pin jinja2 to an earlier version. As long as the docs don't break with the newer version of Sphinx, that would be my preferred solution. Anyone fixing this will need to update the version of Sphinx in the file above (
doc/requirements.txt
) then build the docs using that version and if they build without issue, look at the resulting docs (usemake
, particularlymake html
in thedocs/
directory) to make sure they look ok (look particularly at the checker tables, as those are probably most likely to break). If they don't look ok, make any necessary changes to bring them in compliance with the newer versions required.This is probably a 1 line change + some time confirming that everything is fine, so I'll leave it flagged as a "good first issue"
The text was updated successfully, but these errors were encountered: