https://bugzilla.redhat.com/show_bug.cgi?id=2092637 --- Comment #5 from Ben Beasley <code@xxxxxxxxxxxxxxxxxx> --- (In reply to Major Hayden 🤠 from comment #2) > I was packaging the docs previously for these google cloud packages, but > then I ended up in some challenging situations with sphinx trying to refer > to other bits of documentation that it couldn't reach during an RPM build. If you wanted to package the documentation, you would need to ask sphinx for PDF output instead of HTML (see bug 2006555 and the linked packaging mailing list discussion). Then you could do something like: > # Drop intersphinx mappings, since we can’t download remote inventories and > # can’t easily produce working hyperlinks from inventories in local > # documentation packages. > echo 'intersphinx_mapping.clear()' >> docs/conf.py to stop it from complaining about intersphinx mappings. See https://src.fedoraproject.org/rpms/python-aiosignal/ for an example, and let me know if you want a PR to enable documentation on any of these packages. However, packaging generated documentation is *not* required, and in many cases may not be worth the trouble. -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2092637 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
