Hi @codonell,

thanks for contacting Release Engineering. I am slightly confused are you asking us to do a mass rebuild before the scheduled one? If so do you expect us to rebuild a specific set of packages? Like everything that depends on gcc&binutils, or to rebuild everything in Fedora twice?

Hi @codonell,

thanks for contacting Release Engineering. I am slightly confused are you asking us to do a mass rebuild before the scheduled one? If so do you expect us to rebuild a specific set of packages? Like everything that depends on gcc&binutils, or to rebuild everything in Fedora twice?

My apologies. Please let me clarify. I'm not asking for a second mass rebuild. I am only asking that you carry out the mass rebuild as-planned in the schedule. This request is here to avoid the existing mass-rebuild from being removed from the schedule in the event it was considered not-required.

Please consider the "GNUToolchainF39" system-wide change request as having a dependency on the existing mass-rebuild in the schedule.

Thanks for the clarification, the mass rebuild will go along as scheduled and we will include the latest toolchain builds available at that time.

Hi @codonell,

are all the tool chain changes ready for the scheduled mass rebuild that will happen on 2023-07-18 10:30 UTC ?

Hi @codonell,

are all the tool chain changes ready for the scheduled mass rebuild that will happen on 2023-07-18 10:30 UTC ?

In general the Toolchain is a GO:

• gcc 13.1.1 is ready
• binutils 2.40 is ready
• glibc 2.38 snapshot is ready and can be used to rebuild @critical-path-base+@critical-path-build+@critical-path-compose
• gdb 13.2 is ready

When gcc 13.2 becomes available (August) we'll update to that to include additional bug fixes. When the final released version of glibc 2.38 releases on August 1st we'll pickup the release (minimal delta from what we have) to have finalized ABI guarantees.

We are ready for the mass rebuild.

Amazing the rebuild will start as scheduled.