On 2025-01-28 06:00, Vít Ondruch wrote:
This is debatable. Realistically, failure due to GCC does not need to be fixed everywhere until really needed. It is good to have it fixed in Rawhide to be ready for backport when needed.
Build failures don't *have* to be fixed right away, but in practice I don't think too many packagers would want to let such failures linger around too long. Especially for packages that tend to get frequent security updates; they would want builds to always succeed so that they don't block future updates.
So I reckon it is debatable if fixing *all* FTBFS is a goal, but maybe all Base OS FTBFS do in practice need to be fixed before release, although not necessarily before branching.
Sid -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
