English Italian
Fails to build from source, Fails to install
This page describes *the policy for packages that no longer build or install* and need developer attention.
The schedule for most releases of Fedora includes a mass rebuild (e.g. link:https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild[Fedora 27 Mass Rebuild], link:https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild[Fedora 28 Mass Rebuild]) to update the packages with new features of the compiler, packaging, build flags, etc. This serves as a convenient opportunity to detect all packages which no longer build properly.
Glossary
FTBFS
Fails To Build From Sources
FTI
Fails To Install (usually due to broken dependencies)
Package removal for long-standing FTBFS and FTI bugs
Packages which fail to build or fail to install will be orphaned and/or retired after a period of time.
If a package *fails to build from sources* or *fails to install*,
any concerned party can *file a bug* in Bugzilla blocking a FTBFS/FTI tracker, providing information about the failure.
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.
One bug can block multiple trackers if convenient. Reporters are encouraged to search for duplicates first.
Maintainers should either fix and close the bug or acknowledge that
they are working on a solution by setting the state to ASSIGNED.
If an FTBFS or FTI bug remains in the NEW state for at least *1
week*, any concerned party can set a *NEEDINFO* asking the maintainer to respond.
If the bug remains in NEW state for at least another 3 weeks after