#8837 Rebase the binutils package to 2.33
Closed: Fixed 4 years ago by mohanboddu. Opened 4 years ago by nickc.

  • Describe the issue
    A new release of the GNU Binutils is about to happen (version 2.33). This change request
    is to alert people to the change and allow a chance for any concerns to be raised. (None are expected though).

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

2019/10/07

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

2020/01/30

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

The binutils in rawhide will be an older version, with fewer bug fixes and features.


@nickc Please update the ticket with the change request url when its filed.

Thanks.

Metadata Update from @mohanboddu:
- Issue tagged with: changes

4 years ago

@nickc Based on the change request I dont think mass rebuild is required for this change. Can you confirm?

Thanks.

Metadata Update from @mohanboddu:
- Issue tagged with: f32

4 years ago

@nickc Based on the change request I dont think mass rebuild is required for this change. Can you confirm?

Actually no, a mass rebuild is needed. It does not have to be specifically for this update, but it must happen before the f32 branch is cut. The binutils package provides the assembler and linker used when building most other packages, and if there is a bug in either of these tools then there could be a serious problem.

@nickc Based on the change request I dont think mass rebuild is required for this change. Can you confirm?

Actually no, a mass rebuild is needed. It does not have to be specifically for this update, but it must happen before the f32 branch is cut. The binutils package provides the assembler and linker used when building most other packages, and if there is a bug in either of these tools then there could be a serious problem.

Thanks for confirming @nickc

Metadata Update from @mohanboddu:
- Issue tagged with: mass rebuild

4 years ago

Closing this ticket as it is included in mass rebuild.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata