|
|
| (8 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| {{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
| | = Binutils 2.35 = |
| | |
| <!-- Self Contained or System Wide Change Proposal?
| |
| Use this guide to determine to which category your proposed change belongs to.
| |
| | |
| Self Contained Changes are:
| |
| * changes to isolated/leaf package without the impact on other packages/rest of the distribution
| |
| * limited scope changes without the impact on other packages/rest of the distribution
| |
| * coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
| |
| | |
| System Wide Changes are:
| |
| * changes that does not fit Self Contained Changes category touching
| |
| * changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
| |
| * changing system defaults
| |
| | |
| For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies).
| |
| | |
| We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
| |
| -->
| |
| | |
| <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace -->
| |
| | |
| = Binutils 2.35 <!-- The name of your change proposal --> = | |
|
| |
|
| == Summary == | | == Summary == |
| <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release.
| |
| Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
| |
| Rebase the binutils package from version 2.34 to version 2.35. | | Rebase the binutils package from version 2.34 to version 2.35. |
|
| |
|
| == Owner == | | == Owner == |
| <!--
| |
| For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
| |
| This should link to your home wiki page so we know who you are.
| |
| -->
| |
| * Name: Nick Clifton [https://fedoraproject.org/wiki/User:Nickc] | | * Name: Nick Clifton [https://fedoraproject.org/wiki/User:Nickc] |
| | * Email: nickc@redhat.com |
|
| |
|
| <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
| |
| * Email: nickc@redhat.com
| |
|
| |
|
| <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
| | == Current status == |
| * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
| | [[Category:ChangeAcceptedF34]] |
| -->
| |
|
| |
|
| <!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
| |
| * Product:
| |
| * Responsible WG:
| |
| -->
| |
|
| |
|
| == Current status ==
| | [[Category:SystemWideChange]] |
| [[Category:ChangeReadyForWrangler]] | |
| <!-- When your change proposal page is completed and ready for review and announcement -->
| |
| <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
| |
| <!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
| |
| <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
| |
|
| |
|
| <!-- Select proper category, default is Self Contained Change -->
| |
| [[Category:SelfContainedChange]]
| |
| <!-- [[Category:SystemWideChange]] -->
| |
|
| |
|
| * Targeted release: Fedora 34 | | * Targeted release: Fedora 34 |
| Line 67: |
Line 25: |
| CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development |
| --> | | --> |
| * FESCo issue: <will be assigned by the Wrangler> | | * FESCo issue: [https://pagure.io/fesco/issue/2423 #2423] |
| * Tracker bug: <will be assigned by the Wrangler> | | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1854613 #1854613] |
| * Release notes tracker: <will be assigned by the Wrangler> | | * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/526 #526] |
|
| |
|
| == Detailed Description == | | == Detailed Description == |
|
| |
|
| <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
| |
| Switch the binutils package from being based on the 2.34 release of the GNU binutils to | | Switch the binutils package from being based on the 2.34 release of the GNU binutils to |
| being based on the 2.35 release. This release will bring in numerous bug fixes, as well | | being based on the 2.35 release. This release will bring in numerous bug fixes, as well |
| Line 83: |
Line 40: |
|
| |
|
| == Benefit to Fedora == | | == Benefit to Fedora == |
|
| |
| <!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved?
| |
|
| |
| Be sure to include the following areas if relevant:
| |
| If this is a major capability update, what has changed?
| |
| For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
| |
| If this is a new functionality, what capabilities does it bring?
| |
| For example: This change allows package upgrades to be performed automatically and rolled-back at will.
| |
| Does this improve some specific package or set of packages?
| |
| For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
| |
| Does this improve specific Spins or Editions?
| |
| For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
| |
| Does this make the distribution more efficient?
| |
| For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
| |
| Is this an improvement to maintainer processes?
| |
| For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
| |
| Is this an improvement targeted as specific contributors?
| |
| For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
| |
|
| |
| When a Change has multiple benefits, it's better to list them all.
| |
|
| |
| Consider these Change pages from previous editions as inspiration:
| |
| https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
| |
| https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
| |
| https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
| |
| https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
| |
| https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
| |
| -->
| |
|
| |
|
| The main benefit will be the bug fixes and the improvement to the linker and assembler. | | The main benefit will be the bug fixes and the improvement to the linker and assembler. |
| Line 116: |
Line 45: |
| == Scope == | | == Scope == |
| * Proposal owners: | | * Proposal owners: |
| <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
| |
|
| |
| Change the source parameter in the binutils.spec rpm and adjust the local patches to take account of the bugs that are now already fixed. | | Change the source parameter in the binutils.spec rpm and adjust the local patches to take account of the bugs that are now already fixed. |
| This is a significant change to the underlying tools used to build Fedora and so there should be a mass rebuild in order for the changes to be noticed across the system. | | This is a significant change to the underlying tools used to build Fedora and so there should be a mass rebuild in order for the changes to be noticed across the system. |
|
| |
|
|
| |
|
| * Other developers: None <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | | * Other developers: None |
| <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
| |
| | |
| * Release engineering: [https://pagure.io/releng/issues/9539] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue.
| |
| The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
| |
|
| |
|
| | * Release engineering: [https://pagure.io/releng/issue/9539] |
| A mass rebuild will be required. | | A mass rebuild will be required. |
|
| |
|
| * Policies and guidelines: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | | * Policies and guidelines: No documents need to be updated. |
| <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. -->
| |
| | |
| No documents need to be updated. | |
|
| |
|
| * Trademark approval: N/A (not needed for this Change) | | * Trademark approval: N/A (not needed for this Change) |
| <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
| |
|
| |
|
| == Upgrade/compatibility impact == | | == Upgrade/compatibility impact == |
| <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
| |
|
| |
| The binutils are backwards compatible with previous releases, so no changes should be necessary. | | The binutils are backwards compatible with previous releases, so no changes should be necessary. |
|
| |
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
|
| |
|
| == How To Test == | | == How To Test == |
| <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.
| |
|
| |
| Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
| |
|
| |
| A good "how to test" should answer these four questions:
| |
|
| |
| 0. What special hardware / data / etc. is needed (if any)?
| |
| 1. How do I prepare my system to test this change? What packages
| |
| need to be installed, config files edited, etc.?
| |
| 2. What specific actions do I perform to check that the change is
| |
| working like it's supposed to?
| |
| 3. What are the expected results of those actions?
| |
| -->
| |
|
| |
| The binutils package does include its own set of testsuites which check basic functionality. | | The binutils package does include its own set of testsuites which check basic functionality. |
| The real test however is by rebuilding other packages which depend upon the binutils, or | | The real test however is by rebuilding other packages which depend upon the binutils, or |
| Line 166: |
Line 67: |
| broken anything. | | broken anything. |
|
| |
|
|
| |
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
|
| |
|
| == User Experience == | | == User Experience == |
| <!-- If this change proposal is noticeable by users, how will their experiences change as a result?
| |
|
| |
| This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
| |
|
| |
| Describe what Users will see or notice, for example:
| |
| - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
| |
| - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
| |
| - Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
| |
| - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
| |
| -->
| |
|
| |
| The change should not be noticeable to the user. | | The change should not be noticeable to the user. |
|
| |
|
| == Dependencies == | | == Dependencies == |
| <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? -->
| |
|
| |
| This update has no hard dependencies on any other package. | | This update has no hard dependencies on any other package. |
| There are other packages that do depend upon the binutils however. Most notably gcc and redhat-rpm-config. | | There are other packages that do depend upon the binutils however. Most notably gcc and redhat-rpm-config. |
|
| |
|
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
|
| |
|
| == Contingency Plan == | | == Contingency Plan == |
|
| |
| <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->
| |
| * Contingency mechanism: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
|
| |
| Revert to the 2.34 binutils as currently used in rawhide. This work can be done by me, should it prove necessary. | | Revert to the 2.34 binutils as currently used in rawhide. This work can be done by me, should it prove necessary. |
|
| |
|
| <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. -->
| | * Contingency deadline: Beta freeze. |
| * Contingency deadline: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | | * Blocks release? No |
| | |
| Beta freeze. | |
| | |
| <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
| |
| * Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |
| * Blocks product? None <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
| |
|
| |
|
| == Documentation == | | == Documentation == |
| <!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. -->
| | This rebase brings with it many bug fixes, plus the following notable new features: |
| | | * The assembler now supports the generation of DWARF-5 format line number tables. |
| Documentation is not currently available, due to the fact that the 2.35 release has not yet been created.
| | * Readelf will now display a visual indication when it is forced to truncate a symbol's name in order to fit into the 80-column display limit. |
| (It is hoped that the release will happen before the Fedora 34 mass rebuild).
| | * Readelf now also has a "lint" mode to enable extra checking of binary files. |
| | | * The BFD based now linker has the ability to make specific symbols dynamic. |
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| | * The linker's -Map command line option can be given a directory name and the linker will create a map file inside that directory. |
|
| |
|
| == Release Notes == | | == Release Notes == |
