releng/tickets

F44 system-wide change: GNU Toolchain update for F44 https://fedoraproject.org/wiki/Changes/GNUToolchainF44 #13102

New issue

Closed

opened 2025-11-24 17:55:10 +00:00 by codonell · 4 comments

codonell commented

2025-11-24 17:55:10 +00:00

Please note that we are not asking a new mass rebuild, just that the current F44 mass rebuild continue as planned or is moved to a later date in January 2026.

Please note that the current scheduled mass rebuild of 2026-01-07 is sufficiently early that the Fedora GNU Toolchain teams likely cannot be ready that early, and it may negatively impact the quality and outcomes of the mass rebuild.

Describe the issue:

We are requesting a mass rebuild for the toolchain update to the latest gcc, binutils, glibc and gdb.

When do you need this? (YYYY/MM/DD)

By the mass rebuild scheduled date (2026-01-07)

When is this no longer needed or useful? (YYYY/MM/DD)

After the mass rebuild is complete (2026-01-07)

If we cannot complete your request, what is the impact?

gcc 16.0, binutils 2.46, glibc 2.44, gdb 16.3 would still be a part of F44, but some packages would not have been built against the updated components and may fail to build at a later date or require additional work to integrate correctly into GA.

Notes:

glibc has been doing weekly rawhide rebases from upstream for the last 6 months as usual and fixing integration issues as they arise.
binutils has been doing weekly rawhide rebases from upstream for the last 6 months and fixing integration issues as they arise.
gcc 15.2 is a point release and should not contain any high risk items.
gdb 16.3 is a new release but will only impact debuginfo modifications during the build.

Please note that we are not asking a new mass rebuild, just that the current F44 mass rebuild continue as planned or is moved to a later date in January 2026. Please note that the current scheduled mass rebuild of 2026-01-07 is sufficiently early that the Fedora GNU Toolchain teams likely cannot be ready that early, and it may negatively impact the quality and outcomes of the mass rebuild. Describe the issue: We are requesting a mass rebuild for the toolchain update to the latest gcc, binutils, glibc and gdb. When do you need this? (YYYY/MM/DD) - By the mass rebuild scheduled date (2026-01-07) When is this no longer needed or useful? (YYYY/MM/DD) - After the mass rebuild is complete (2026-01-07) If we cannot complete your request, what is the impact? - gcc 16.0, binutils 2.46, glibc 2.44, gdb 16.3 would still be a part of F44, but some packages would not have been built against the updated components and may fail to build at a later date or require additional work to integrate correctly into GA. Notes: - glibc has been doing weekly rawhide rebases from upstream for the last 6 months as usual and fixing integration issues as they arise. - binutils has been doing weekly rawhide rebases from upstream for the last 6 months and fixing integration issues as they arise. - gcc 15.2 is a point release and should not contain any high risk items. - gdb 16.3 is a new release but will only impact debuginfo modifications during the build.

jnsamyak added the

labels

2025-11-27 06:03:02 +00:00

jnsamyak self-assigned this

2025-11-27 06:03:06 +00:00

jnsamyak commented

2025-11-27 06:03:59 +00:00

Owner

Hey I'll bring it up to the next releng weekly call, and will discuss about the posible outcomes.

Hey I'll bring it up to the next releng weekly call, and will discuss about the posible outcomes.

kevin commented

2025-12-09 18:49:25 +00:00

Owner

Note that schedule is somewhat wrong.

See https://pagure.io/fedora-pgm/schedule/issue/219 about that.

The actual schedule is supposed to have a 'tools changes land' on 2026-01-07 and then 'mass rebuild' on 2026-01-14.

Still very tight and possibly still an issue, but at least another week of time and we can revisit the schedule if needed after the holidays. Hopefully that helps!

Note that schedule is somewhat wrong. See https://pagure.io/fedora-pgm/schedule/issue/219 about that. The actual schedule is supposed to have a 'tools changes land' on 2026-01-07 and then 'mass rebuild' on 2026-01-14. Still very tight and possibly still an issue, but at least another week of time and we can revisit the schedule if needed after the holidays. Hopefully that helps!

jnsamyak commented

2025-12-12 07:25:47 +00:00

Owner

@codonell, do you think we could fit that in this timeline?

@codonell, do you think we could fit that in this timeline?

jnsamyak added the

labels

2025-12-12 07:26:11 +00:00

jnsamyak added this to the Fedora Releng Sprint 7 project

2026-01-22 12:17:42 +00:00

jnsamyak commented

2026-01-22 12:18:12 +00:00

Owner

I think this can be closed now, with mass rebuild completed and the blockers being accounted for.

I think this can be closed now, with mass rebuild completed and the blockers being accounted for.

jnsamyak closed this issue

2026-01-22 12:18:12 +00:00

Sign in to join this conversation.

No labels

change-noreleng

Fixed with Explanation

Insufficient data

mini-initiative

waiting on external

No milestone

No project

No assignees

3 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

releng/tickets#13102

No description provided.