The x86_64 KDE live image from the most recent Beta RC compose (Beta 1.4) is 1490026496 bytes. The specified maximum size for KDE live images on https://fedoraproject.org/wiki/Releases/25/Spins is 1.4GB, i.e. 1400000000 bytes. The 26/Spins page has not yet been created, it seems, so I'm going with the 25 policy. This is an automatic blocker: "Any release-blocking Beta or Final TC/RC image exceeding its target size (failures of QA:Testcase_Mediakit_ISO_Size)" - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Automatic_blockers . We *could* just change the KDE target size to resolve this, since it seems the policy about revisiting the Spins list for each release wasn't done for 26 so I guess in theory it's reasonable to say the window to change the target size is still open. 1.4GB is a fairly random target size, it doesn't map to any media I can think of; I think it was originally arrived at just by doubling the size of a CD (700MB).
Rex, Kevin, thoughts on changing the target size? It's either that or slip a week, really. I do apologize for not filing this sooner, I hadn't thought to check the size check results :(
CCing some Usual Suspects (TM)
I do not maintain the live image anymore, I will let Rex decide how to deal with this issue. I am just very unhappy about the creeping bloat. The size of the images keeps increasing with every release.
Since the size is arbitrary (as far as I can tell), I think it's fine to change the target size. The next highest size that makes sense to me would be 2GB (to fit on 2GB flash drives... if any of those still exist or are being handed out).
Discussed at 2017-06-01 Fedora 26 Beta Go/No-Go meeting #2, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-2/2017-06-01/f26-beta-go-no-go-meeting.2017-06-01-17.00.log.html . Rex Dieter, as KDE SIG representative, affirmed that the target size for Fedora 26 is changed to 2GB, so this bug is no longer a blocker.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.