On Wed, Jan 07, 2026 at 06:50:24AM -0500, Siddhesh Poyarekar wrote:
> > It may actually work this way, but only if only one party is doing that.
> > As soon as we have two changes, picking breakages apart and resolving
> > them will be tedious. That's why we have side-tags in order to isolate
> > the effects of different changes.
>
> Maybe for F46 we could try allowing Ada packages to build into the early
> side tag and live with breakages if we can't get to them. It has the risk
> of breaking all of the prebuild task[2] that runs during the holidays and
> thus preventing *any* earlier feedback though.
Maybe we should have 2 side tags, one for just gcc/libtool/annobin like
this year, and another one based on that for the Ada rebuilds, and before
we tag the former into rawhide tag everything from the Ada rebuild tag
into the first tag.
The desire not to have random other packages tagged into the side tag
was that we then don't need to be stuck when e.g. rawhide has newer versions
of those packages (rebuilt with older compiler) etc.
Jakub
--
_______________________________________________
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
