Skip to content
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 build failures with Sphinx 3 #4008

Closed
stratakis opened this issue Apr 21, 2020 · 2 comments · Fixed by #4010
Closed

Docs build failures with Sphinx 3 #4008

stratakis opened this issue Apr 21, 2020 · 2 comments · Fixed by #4010

Comments

@stratakis
Copy link

bodhi fails to build from source on Fedora with Sphinx 3 series.

Downstream bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1823739

Error:
Warning, treated as error:
/builddir/build/BUILD/bodhi-5.1.1/bodhi/server/models.py:docstring of bodhi.server.models.Bug.url:1:duplicate object description of bodhi.server.models.Bug.url, other instance in developer/docblocks/bodhi.server.models, use :noindex: for one of them
make: *** [Makefile:51: html] Error 2
make: Leaving directory '/builddir/build/BUILD/bodhi-5.1.1/docs'
error: Bad exit status from /var/tmp/rpm-tmp.A6849v (%build)

Sphinx 3 changelog: https://www.sphinx-doc.org/en/master/changes.html#release-3-0-0-released-apr-06-2020

@mattiaverga
Copy link
Contributor

Possibly related to #1995

I think we can just drop the url column, since Bug.url is provided via the url property. I don't see anything in the code that stores the url in db.

@stratakis
Copy link
Author

Trying a new build with either the patch applied or with version 5.3.0 I now get:

/builddir/build/BUILD/bodhi-5.3.0/bodhi/messages/schemas/base.py:docstring of bodhi.messages.schemas.base.BuildV1.nvr:1:duplicate object description of bodhi.messages.schemas.base.BuildV1.nvr, other instance in server_api/messages/base, use :noindex: for one of them

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants