On Tue, Jul 25, 2023 at 06:45:41PM +0200, Miro Hrončok wrote: > IMHO it is what the policy says, quite explicitly: > > From https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs > > """ > Cca six weeks before the Fedora N mass branching, packages that weren’t > successfully rebuilt at least in Fedora N-2 are collected and weekly > reminders are sent to affected maintainers and the Fedora devel mailing > list. > > Cca a week before the Fedora N mass branching, packages that weren’t > successfully rebuilt at least in Fedora N-2 will be retired assuming there > have been at least 5 warnings on the devel mailing list. The bug status has > no effect on this retirement. This can be requested via a releng issue. > """ > > When I included glibc32 in the list, it wasn't successfully rebuilt at least > in Fedora 37. > > We could argue what "successfully rebuilt" actually means, but when I wrote > that policy, the spirit was "an actual built shipped to Fedora users" rather > than "a Koschei rebuild". Sure, but glibc32 is in fact never shipped to Fedora users. :) We explicily block it in pungi so it never goes out. It's a buildsystem implementation detail. > I see you rebuilt it now, thanks. > > Should I open a releng ticket to include this package in the next mass rebuild? I suppose we could rebuild it, I don't think that would matter any? Or would it? Florian? kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
