On Wed, 14 Jan 2026 at 18:49, Adam Williamson <[email protected]> wrote: > > On Wed, 2026-01-14 at 19:43 +0100, Fabio Valentini wrote: > > On Wed, Jan 14, 2026 at 7:40 PM Jonathan Wakely <[email protected]> wrote: > > > > > > Right, that's what I mean. The builds I did don't need to be in rawhide. > > > > > > But the changes to the specs have still been pushed to dist-git, so > > > when those packages are in the mass rebuild, the new versions of the > > > packages will get built. > > > > Yes, but the new versions of the packages (from git) would get built > > against the *old* boost (from the rawhide buildroot). > > Well, if the boost 1.90.0 bump is still committed to dist-git, boost > would get bumped back to 1.90.0 as part of the mass rebuild, which > would also be bad.
That's the point I've been trying to make. Just untagging the builds I already did won't stop the new boost being included in the mass rebuild, and depending on the order that its revdeps are built, some of them will also use the new boost. > > We probably need to commit to *either* fixing the critical deps before > the mass rebuild happens and doing the mass rebuild with 1.90.0, *or* > reverting the boost soname bump in git to ensure the mass rebuild is > done with the old boost, before the mass rebuild starts. Which is what I was hoping to achieve, but I only got fesco approval less than 24 hours before the mass rebuild was due to start. So then I rushed things and screwed up. I was really hoping that the new boost would be in the buildroot before the mass rebuild, but I suppose I can just back everything out and try again in a few weeks. -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
