https://bugzilla.redhat.com/show_bug.cgi?id=1888345
--- Comment #3 from Andy Mender andymenderunix@gmail.com ---
Only way to avoid this is to not ship the docs. I'm wondering why this doesn't happen for other packages which depends sphinx-rtd-theme as the config for the docs looks pretty "standard".
Some packages which generate Sphinx docs bundle font files like Font Awesome and some don't. Some also download extra artifacts during the doc building process. I think it's often overlooked by upstream, because unless packaged, neither is an issue which prevents direct software usage.
I think we have the following options: 1. Remove the docs in the %build stage and not package them at all. 2. Remove the font files and link them in from system font packages. Below are the ones used in python-hbmqtt: - google-roboto-slab-fonts - fontawesome-fonts-web (probably also: fontawesome-fonts) - lato-fonts 3. Suggest to upstream to use fontconfig for font file discovery.
If option 2. actually works, it could set a precedence for other similar packages.
Extra docs from the packaging guidelines: - https://docs.fedoraproject.org/en-US/packaging-guidelines/#bundling - https://docs.fedoraproject.org/en-US/packaging-guidelines/FontsPolicy/#_depe... - https://fedoraproject.org/wiki/Shipping_fonts_in_Fedora_(FAQ)#What_if_my_pac... - https://fedoraproject.org/wiki/Shipping_fonts_in_Fedora_(FAQ)#But_I_really_d...