English Italian
A bug about build failure needs to block the FTBFS tracker for the appropriate release, eg. F30FTBFS for Fedora 30, see list below.
A bug about installation failure needs to block the FTI tracker for the appropriate release, eg. F30FailsToInstall for Fedora 30, see list below.
any concerned party can *file a bug* in Bugzilla blocking a FTBFS/FTI tracker, providing information about the failure.
Anytime a releng ticket is open, please cross reference it from the bug report.
A week before the scheduled *beta freeze*, any packages which have
Build the package. The fixed package will land in rawhide, generally the next day. If branching has already occurred, also fix the build in branched.
Cca a week before the Fedora N *mass branching*, packages that weren't
Cca six weeks before the Fedora N *mass branching*, packages that weren't
(Effectively, packages that fail to build will be retired after 14 weeks or sooner if there is no maintainer response and the package is orphaned, or after 13 months if the maintainer responds but the package is not fixed.)
Example FTBFS retirement
F11 was handled by Release Engineering, no FTBFS bugs were filed. link:http://jkeating.fedorapeople.org/needed-f11-rebuilds.html[] (link:https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild[Fedora 11 Mass Rebuild])
F22?
F23? (link:https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild[Fedora 23 Mass Rebuild])
F27? (link:https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild[Fedora 27 Mass Rebuild])
Fails to build from source, Fails to install
Fails To Build From Sources
Fails To Install (usually due to broken dependencies)
Find an existing bug for that package describing the problem. Set your bug to "Depends on" that other bug. Do not change the component of your bug to the other package, or you will get more FTBFS bugs created against you.
Fix the problems uncovered and commit the changes.
FTBFS