Description

JelleZijlstra

opened on Jun 7, 2023

Issue body actions

On all 3.11 PRs that touch non-docs files (e.g. #105417), the Check if generated files are up to date check is currently failing on the check grep "Generated by GNU Autoconf 2.69" configure.

This is because d2340ef, which created 3.11.4, updated configure to be generated by Autoconf 2.71. @pablogsal why was this done? Should we update the build.yml file to check for 2.71 instead of 2.69?

Linked PRs

• [3.11] gh-105455: Regen configure with GNU Autoconf 2.69 #105467
• [3.11] gh-105455: Bump to GNU Autoconf v2.71 (#104925) #105469

Activity

1. JelleZijlstra

   added

   type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error

   buildThe build process and cross-buildThe build process and cross-build

   3.11only security fixesonly security fixes

   on Jun 7, 2023
2. ned-deily commented on Jun 7, 2023

   

   ned-deily

   on Jun 7, 2023

   Member

   More actions

   This is probably a side effect of the most recent PRs for #89886 which probably updated the container used to do autoconf operations. @erlend-aasland
3. pablogsal commented on Jun 7, 2023

   

   pablogsal

   on Jun 7, 2023

   Member

   More actions

   @pablogsal why was this done?

   The release script runs it by running the autoconf step here:

   https://github.com/python/release-tools/blob/8485d3b4d77a2559cbb3cf2e63dee43070327d50/run_release.py#L414-L429
4. erlend-aasland commented on Jun 7, 2023

   

   erlend-aasland

   on Jun 7, 2023

   Contributor

   More actions

   This is probably a side effect of the most recent PRs for #89886 which probably updated the container used to do autoconf operations. @erlend-aasland

   We did not update the container. We just updated the CI and make to use the 271 tagged container. The release tools should use the correct tag depending on which release it is building.
5. erlend-aasland commented on Jun 7, 2023

   

   erlend-aasland

   on Jun 7, 2023

   Contributor

   More actions

   Either we reset configure using GNU Autoconf 2.69, or we backport the Autoconf 2.71 bump to 3.11. I guess the former is preferred, but the latter creates less churn. I can create PRs for both.
6. erlend-aasland

   added 3 commits that reference this issue on Jun 7, 2023

   [3.11] pythongh-105455: Regen configure with GNU Autoconf 2.69

   787cba4

   [3.11] pythongh-105455: Bump to GNU Autoconf v2.71 (python#104925)

   2d54f33

   [3.11] gh-105455: Regen configure with GNU Autoconf 2.69 (#105467)

   2ffeb0e
7. erlend-aasland commented on Jun 7, 2023

   

   erlend-aasland

   on Jun 7, 2023

   Contributor

   More actions

   Resolved with:

   • [3.11] gh-105455: Regen configure with GNU Autoconf 2.69 #105467
8. erlend-aasland

   closed this as completedon Jun 7, 2023

Issue actions