Mate live x86_64 image https://kojipkgs.fedoraproject.org/compose/branched/Fedora-31-20190928.n.0/compose/Spins/x86_64/iso/Fedora-MATE_Compiz-Live-x86_64-31-20190928.n.0.iso from compose Fedora-31-20190928.n.0 is 2141192192 bytes, exceeding the maximum size 2000000000.Canonical maximum sizes can be found at https://fedoraproject.org/wiki/Releases/31/Spins and https://fedoraproject.org/wiki/Releases/31/ReleaseBlocking . This check is run by the 'relval' tool, which has its own list of maximum sizes derived from those pages. If the maximum size used for this comparison is wrong, please add a comment and file a bug against relval at https://pagure.io/fedora-qa/relval/issues and it will be corrected. If you believe the canonical maximum size for an image should be changed, please follow the appropriate process before filing a relval bug.
re-assigning to a MATE component.
Hi Adam, i have no idea why this happens because i didn't change MATE groups in comps or kickstart configs. Looks like other general fedora packages has increased their size. Maybe Asian font packages or firefox? Any way, i have increased maximum spin size to 3GB to fix the comparison. https://fedoraproject.org/wiki/Releases/31/Spins#Official_Fedora_Spins Hopefully this is sufficient to solve this issue?
This didn't happen just yesterday, we just only deployed the bug filing robot recently. It has been 2.1G since at least May - https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190502.n.0_Installation has it at 2118221824 bytes. Bumping the max size is a choice, of course, if you don't actually care about fitting on 2GB USB sticks or booting on systems with little memory (AIUI the entire live image is basically loaded into RAM, so if your image is over 2GB you're probably not going to boot on a system with less than 4GB of RAM for e.g.)
Size is OK for me.
By '3 GB' did you mean 3221225472 bytes or 3000000000 bytes?
I didn't change the unit, only value was increased. Choose what matches best for you or change the units at wiki page when this is a killer for you ;)
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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.
No point keeping this open.