Unmerged PRs with CMake 4 fixes

[Marcin Juszkiewicz]

Hi everyone,

As I understand it, Fedora 45 will comfortably use F44 packages as long
as they work. Consequently, our next major mass-rebuild likely won't
occur until F46 or F47, which is precisely when a significant number of
packages are expected to FTBFS due to incoming CMake 4 changes.

To help mitigate this, Cristian Le has already done some incredible
work and opened an extensive list of PRs addressing CMake 4 fixes.
Unfortunately, many of these pull requests are now 4 to 12 months old
and are still awaiting a response or review from the respective maintainers.

Do we really need to wait for the next official mass-rebuild to see
movement on these, or let them drift into the two-release "retire by
FTBFS" pipeline? Given that the fixes are already sitting in Pagure,
could this be a good candidate for a coordinated Proven Packager effort
to review and land these outstanding PRs early?

I would love to hear thoughts on how we can proactively address this
backlog before it becomes a major bottleneck for the distribution.

[Marcin Juszkiewicz]

W dniu 22.06.2026 o 16:37, Marcin Juszkiewicz pisze:
> Hi everyone,
>
> As I understand it, Fedora 45 will comfortably use F44 packages as long
> as they work. Consequently, our next major mass-rebuild likely won't
> occur until F46 or F47, which is precisely when a significant number of
> packages are expected to FTBFS due to incoming CMake 4 changes.

Ok, I got corrected (on Matrix) that mass-rebuild now happens every 
cycle. Which will bring those FTBFS events sooner than later.

[Fabio Valentini]

On Mon, Jun 22, 2026 at 4:59 PM Marcin Juszkiewicz
 wrote:
> W dniu 22.06.2026 o 16:37, Marcin Juszkiewicz pisze:
> > Hi everyone,
> >
> > As I understand it, Fedora 45 will comfortably use F44 packages as long
> > as they work. Consequently, our next major mass-rebuild likely won't
> > occur until F46 or F47, which is precisely when a significant number of
> > packages are expected to FTBFS due to incoming CMake 4 changes.
>
> Ok, I got corrected (on Matrix) that mass-rebuild now happens every
> cycle. Which will bring those FTBFS events sooner than later.

Note that the mass rebuild is not the *only* way to cause FTBFS bugs
to be filed.
Anybody can do it. And I think they should get processed the same way
as those filed after the mass rebuild, as long as they Block the
relevant tracking bugs etc.

So if you want to speed things along ... filing FTBFS bugs for those
packages manually is also an option.

Fabio