Description of problem:
If you use Katello or RedHat Satellite to sync the Fedora 32 repository using an On Demand policy, the sync will fail due to exceeding the maximum size of the MongoDB document. A member of the Pulp project identified sagemath-doc-en-9.0-2.fc32.x86_64.rpm as containing a lot of files and being the offending RPM.
While the deficiency is with another project, I'm curious if it could be revealing a build/packaging error in the SageMath EN documentation.
When comparing sagemath-doc-en-9.0-2.fc32.x86_64.rpm against the number of files in Fedora 31's sagemath-doc-en-8.8-6.fc31.x86_64.rpm, fc32 has a significant increase.
FC31 = 10,120 files, size 30M
FC32 = 344,834 files, size 168M
I'm not familiar with the Sphinx build process, but is it possible that the build is packaging up source files that are not intended to be in the output resulting in an inflated RPM?
Related Pulp Project issue = https://pulp.plan.io/issues/7449
This appears to be due to mathjax generating a PNG file for every single glyph in some fonts. I really doubt that is necessary. Let me see if I can figure out how to turn that off.
Sagemath is bundling the entire mathjax distribution, including the PNG version, into every bit of documentation, 11 copies in all. I'm about to update sagemath to version 9.2 anyway (as soon as I debug a pesky problem with pari/python-cypari2), and a fix for this issue will be part of that.
FEDORA-2020-f16abf2fb5 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f16abf2fb5
FEDORA-2020-f16abf2fb5 has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f16abf2fb5`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f16abf2fb5
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-f16abf2fb5 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 32 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.