No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangePageIncomplete]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
| Line 32: | Line 32: | ||
<!-- [[Category:SystemWideChange]] --> | <!-- [[Category:SystemWideChange]] --> | ||
* Targeted release: f35 | * Targeted release: f35 | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
| Line 108: | Line 108: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Problems with building 3rd partly software might occur when upgrading to newer version of fedora, where autoconf-2.71 is present. | |||
| Line 142: | Line 143: | ||
- 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. | - 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. | ||
--> | --> | ||
Users will be able to use the newer version (2.71) of autoconf, and building packages with autoconf-2.69 won't be available, as it won't be present on the specific fedora version. | |||
== Dependencies == | == Dependencies == | ||
| Line 147: | Line 150: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Hundreds of packages have build dependency on autoconf, therefore it is a huge step forward for fedora, what should be properly discussed and tested. Autoconf upgrade deadline depends on dependent packages, as if multiple packages are not able to be buit with autoconf-2.71, we cannot proceed with this upgrade. There are also problems with some upstream projects, which require autoconf-2.69 for their build. It is needed to discussed the possible upgrade olso on their side | |||
| Line 152: | Line 156: | ||
<!-- 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. --> | <!-- 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: | * Contingency mechanism: moving this issue to f36, if not successfuly finished in f35 <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: | * Contingency deadline: f35 mass rebuild <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? | * Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Revision as of 12:47, 5 February 2021
Change Proposal Name
Autoconf 2.69 -> 2.71 upgrade
Summary
Upgrading autoconf from version 2.69 to the last upstream version 2.71.
Owner
- Name: Ondrej Dubaj
- Email: odubaj@redhat.com
Current status
- Targeted release: f35
- Last updated: 2021-02-05
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
Upgrading autoconf from version 2.69 to version 2.71 according to new upstream release. Version 2.70 is skipped due to multiple ABI incompatibilities, where some of them were fixed in version 2.71. Years of development differ these two releases, so problems are expected.
Feedback
Benefit to Fedora
Brings a stable and up-to-date version of autoconf according to upsteam release. It is expected, that in the future many upstream development teams will use autoconf-2.71 as their default builder, so we should be prepared for such a step.
Scope
- Proposal owners:
- Other developers:
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Affects hundreds of packages.
Upgrade/compatibility impact
Problems with building 3rd partly software might occur when upgrading to newer version of fedora, where autoconf-2.71 is present.
How To Test
Rebuilding your packages with autoconf-2.71 dependency. For testing, copr can be used https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/packages/
User Experience
Users will be able to use the newer version (2.71) of autoconf, and building packages with autoconf-2.69 won't be available, as it won't be present on the specific fedora version.
Dependencies
Hundreds of packages have build dependency on autoconf, therefore it is a huge step forward for fedora, what should be properly discussed and tested. Autoconf upgrade deadline depends on dependent packages, as if multiple packages are not able to be buit with autoconf-2.71, we cannot proceed with this upgrade. There are also problems with some upstream projects, which require autoconf-2.69 for their build. It is needed to discussed the possible upgrade olso on their side
Contingency Plan
- Contingency mechanism: moving this issue to f36, if not successfuly finished in f35
- Contingency deadline: f35 mass rebuild
- Blocks release? No
Documentation
N/A (not a System Wide Change)