On Tue, Jul 29, 2025 at 7:17 AM Florian Weimer <fwei...@redhat.com> wrote: > > * Adam Williamson: > > > On Mon, 2025-07-28 at 15:33 -0500, Chris Adams wrote: > >> Once upon a time, Adam Williamson <adamw...@fedoraproject.org> 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.
This is basically how Fedora ELN mass-rebuilds occur: our tooling already handles the "look up the last-built Rawhide commit ID" portion, so we just bump the version of the dist-tag (.elnNNN) and have it rebuild everything from the last-successful Rawhide build commit ID. We do this because we treat our dist-tag as a "buildroot version" rather than as a "release version". Fedora Linux on the other hand uses only the major version here, which really means that to do what Florian is suggesting, we'd have to do something like: .fc43~massrebuild and then replace it with `.fc43` when we branch, but that has other problems, among them, we might need to handle the kernel specially, because as we found out in ELN long ago, the kernel stores this string internally and it may exceed the maximum length for the kernel version). Another problem is that we will inevitably ship with some rebuilt packages that retain the ~massrebuild suffix, unless we do another rebuild... which defeats the point. Alternatively. we could do the mass-rebuild with `.fc43` and then change it again to something like `.fc43.0` with the option to bump that minor revision later as many times as we want. This would require new communication/education to the masses to explain the new scheme, but it could work (and open up some opportunities for doing rebuilds without needing to push empty commits). -- _______________________________________________ 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
