Sphinx version has been capped since
I9c45d239e156ec4fb49b5d8bd2404b66155be92b
in order to fix an issue with resolving citations.
Then, in I7e55dcf910e0ba6dd85b565db8cb1ecbdd39634a,
the issue has been fixed by modifying citation references.
So uncap sphinx version.
But sphinx 1.6.1 has another issue (*1),
so leave sphinx 1.6.1 in the blacklist.
*1: https://github.com/sphinx-doc/sphinx/issues/3754
Change-Id: I09acc562bc37edc3c8a40027f7eb359aaa956c32
Related-Bug: #1695127
For some reason this release makes docs builds fail because it
can't resolve citations. The version in upper-constraints, which
we don't use in this repo, is 1.5.6, so blacklisting 1.6.1 seems
fine.
Change-Id: I2b73370876c80a88bd4a48db7fdd6ac23ace4503
Closes-Bug: #1693010
The 0.6.0 release broke on non-ascii characters in the specs,
but it's fixed in 0.6.1, so just blacklist 0.6.0.
Change-Id: I03226ecaa5016f50d89d8ce31c39379f247863a9
Something in 0.6.0 is making docs builds fail because
of non-ascii character parsing. We need to fix those
long-term and uncap this, but let's do it some day when
it's not spec freeze.
Change-Id: I7968790dc5197204de5ce7e38508a866801aef27
For some reason, the gate was failing with the following message:
"WARNING: no "man_pages" config value found; no manual pages will be
written"
I don't know why this has suddenly started happening, but it was
mitigated by 'I97d4ade4'. However, this change didn't fix the root cause
of the issue, which is that 'pbr' defaults to building both html and man
page output and we don't need/want the latter.
Disable the man page builder entirely. This allows us to remove all man
page-related configuration in the process, seeing as it'll never be
used.
Change-Id: I83bb54f413cbad29afb2233043150fb037bca3bd
nova-specs doesn't sync requirements updates from the
global requirements repo and doesn't have the correct
requiremnts ranges for hacking which is pulling in
pbr 2.0.0 which breaks with warnerrors=True (since that
was removed in 2.0.0).
This syncs up the requirements with the latest from
the requirements repo and updates the hacking versions.
Change-Id: I8db1038693c5047ebffd0065055efc5ea211b106
Related-Bug: #1668848
"Detected a distutils installed project" issue is hitting
for argparse for specs repo.
In case of nova specs repo it comes from testtools.
As a workaround, making pbr version > 1.0 so that venv having pip
< 8 and works fine. pbr < 1.0 endup with pip 8 and fails.
pbr < 1.0 has pip explicitly in requirement.txt and trigger
to update the pip to 8.
pbr > 1.0 does not have the requirement.txt thing and does not
trigger pip updates for venv.
This is issue with all specs repo having distutils installed projects
because g-r requirement update does not sync the specs repo requirements.
But that is another thing can be fixed if there is no reason of not
updating specs requirements.
Change-Id: I31a1353d161e5e5687332cd8300ba5dd4f992a67
This was added to work around bug 1091333. A new sphinx has been
released and so this is no longer necessary.
Change-Id: I9107884d964757a9154bdd1feb4ea6df4e9df43e
Add a unit test that will check to make sure all top-level headings
and sub-headings are present.
The downside of this test is that it's going to fail on *every* merged
spec if we add or change a heading to the template.
Co-authored-by: Russell Bryant <rbryant@redhat.com>
Change-Id: I1c15282e166fb3fe2e60fcf063a6cd822a3411ff
Update the nova-specs project to use sphinx. This will allow us to
still write our specs using rst, but also have a nice framework for
rendering and publishing the specs if we choose to.
Change-Id: Ib92231acb28bba44abafb7dd554404f542da13a7
Nguyen Hai