* Adam Williamson: > On Mon, 2025-07-28 at 15:33 -0500, Chris Adams wrote: >> Once upon a time, Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> said: >> > Please, *always*, only land significant changes when you are ready to >> > build and submit them as regular updates. In general, the delta between >> > what is currently in Rawhide and what the mass rebuild will build >> > should be *as small as possible*. Any unbuilt/blocked change sitting in >> > dist-git prior to the mass rebuild is essentially a time bomb. >> >> Would it be feasible to revert packages to "last build in Rawhide" >> before a mass rebuild? > > Feasible? Er. Possibly. Complicated? Probably. The most straightforward way is to change the dist-git tag twice, once immediately after branching rawhide, and once immediately before the mass rebuild. Then the mass rebuild can just resubmit the previously built commit hash because the build will produce a new NVR. A more complicated approach would build off a branch or tag that points to a NVR bump commit on top of the last successful rawhide build. From a maintainer perspective, the branched history does not matter because there are no code changes. Even that isn't *that* complicated. Thanks, Florian -- _______________________________________________ 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
