Project

Profile

Help

Task #1941

Strict/nitpicky sphinx settings break our rpm builds

Added by semyers about 4 years ago. Updated about 2 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Urgent
Assignee:
Category:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation, Pulp 2
Sprint:

Description

This is a post-mortem report of the task of diagnosing and fixing broken builds.


In #950, we turned on strict docs builds, but this ended up breaking our builds.

The problem was that there's no internet access inside the mock buildroot, so when sphinx went to download the intersphinx inventory files it would fail. Normally this triggers a warning, but enabling strict mode promotes all build warnings to errors. It's worth pointing out that the intersphinx downloads have always been failing during RPM build, the only thing new was our strictness.

Strict building is good; at the moment work is ongoing in #950 to modify our docs build process to hopefully (among many other goals) allow us to once again do strict builds with sphinx without breaking the build.

History

#2 Updated by bmbouter over 1 year ago

  • Tags Pulp 2 added

#3 Updated by tuyagavivu about 2 months ago

Especially if you are in a new relationship, it’s best to set a foundation for a positive and healthy relationship from the start. https://dltutuapp.com/tutuapp-download/ https://showbox.run/ https://kodi.software/

Please register to edit this issue

Also available in: Atom PDF