Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=679613
--- Comment #6 from Toshio Ernie Kuratomi a.badger@gmail.com 2011-02-25 10:58:39 EST --- (In reply to comment #3)
Also, I'd appreciate some feedback on how I'm building the docs. Upstream uses Sphinx, which is apparently D/Ling from the web at build time for "intersphinx inventory". My understanding is that koji builds are not allowed network access, nor do we want any external sources anyways. It's not clear to me that these are "sources" in the traditional sense. I'm considering patching out this function, although I frankly don't think I yet fully understand the ramifications of just nuking it entirely or letting it timeout if network access is denied:
intersphinx allows sphinx to create links in documentation between sites. So, for instance, if the documentation you're building references a function from the python stdlib, the sphinx can create a link for that function that points to docs.python.org.
I have a package, python-kitchen, that uses intersphinx and it builds in the build system fine so I think letting that timeout is fine. The only effect should be that the generated documentation won't link to external documents. sphinx should not fail the build just because it can't retrieve the objects.inv file.
If this package doesn't build in koji because f sphinx, let me know and I'll look into it.