I have an idea I'd like to hear you out on how to reduce failures on mass rebuilds.
I think some of the build failures are due to building things out of sequence. I mean, package A buildrequires package B, but since the mass rebuild is performed (AFAIK) alphabetically, package B is rebuilt after, so package A rebuild may fail. The optimal solution would be to have some script that periodically creates a tree of buildrequires dependency for all Fedora packages... but that would require some work. So, I was just thinking, what about to set up a simple repository where we put some text files like: - tier1.txt: - libindi - kpmcore - tier2.txt: - indi-3rdparty-libraries (possibly a tier3.txt too) On mass rebuilds, all packages specified in tier1.txt are rebuilt first, then all packages in tier2.txt (and so on), then all other packages like the current mass rebuild does. In my example this would mean that the correct sequences on rebuild are maintained: - T1: libindi -> T2: indi-3rdparty-libraries -> mass rebuild: indi-3rdparty-drivers (and kstars, stellarium, etc.) - T1: kpmcore -> mass rebuild: kde-partitionmanager I think this could be a simple and quick solution to maintain build chains on mass rebuilds. Thoughts? Mattia -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
