Hide Forgot
For nearly every Fedora release, we fail badly at fulfilling this release criterion: "A spin-kickstarts package which contains the exact kickstart files used to build the release must be present in the release repository. The included kickstarts must define the correct set of release repositories." Almost every time, the package is not built until I notice it's missing and file a blocker bug and generally go chase people around. Neither the release criteria nor the release schedule are secrets. We've been doing this for 25 releases. It should not be beyond us to ensure that this happens for each release without me having to chase people around with a stick at the last minute. Ideally there should be some kind of automated process for building spin-kickstarts regularly, assuming the git repo has changed since the last build. Failing that, at *least*, someone should actually take responsibility for making sure a build is done, say, at the time of Final freeze, and then any time after that when the relevant branch is touched, rebuilding the package. And when I say 'take responsibility', I mean someone should be proactively following the schedule and monitoring the repository to do this, not just waiting around for me or someone else to file a ticket, because I'm getting tired of having to chase around basic crap which should be on someone's checklist for *every damn release we cut*. This isn't aimed at anyone personally, to be clear. I'm just tired of crappy process fails.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
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.