3.11: "Check if generated files are up to date" is failing due to autoconf version

[JelleZijlstra]

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

[ned-deily]

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

[pablogsal]

@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

[erlend-aasland]

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.

[erlend-aasland]

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.

[erlend-aasland]

Resolved with:

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