| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
I think this is a good idea. It doesn't appear there is any reason for the quay.io image anymore given ubuntu-22.04 has a sufficiently good autoconf.
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Let's update https://github.com/python/cpython/blob/d4f83e1e3a19e2f881115f20d58ae6a019ddb48f/Doc/using/configure.rst#generated-files as well.
And backport?
Sorry, something went wrong.
|
@hugovk: I completed the PR to address your review. Would you mind to review the updated PR?
Done.
I added the backport to 3.11 and 3.12 labels. |
Sorry, something went wrong.
|
The main point of this PR is that Tools/build/regen-configure.sh now uses the same container image than the GitHub Action job, so the job doesn't have to run autoreconf in a container, but can run it directly. |
Sorry, something went wrong.
The "Check if generated files are up to date" job of GitHub Actions now runs the "autoreconf -ivf -Werror" command instead of the "make regen-configure" command to avoid depending on the external quay.io server. Add Tools/build/regen-configure.sh script to regenerate the configure with an Ubuntu container image. The "quay.io/tiran/cpython_autoconf:271" container image (https://github.com/tiran/cpython_autoconf) is no longer used.
|
Oh, there is a fix in the Changelog entry causing the Docs job to fail: fixed. |
Sorry, something went wrong.
|
@erlend-aasland: It would be nice if you could review this change, since you made many configure changes last months ;-) |
Sorry, something went wrong.
|
Also, the devguide must be updated. |
Sorry, something went wrong.
There was a problem hiding this comment.
This looks good to me. (I'm a little bit puzzled by the aclocal.m4 and configure changes, but they are also fine.)
Thanks for doing this.
Sorry, something went wrong.
|
IIRC, we did the autoconf version bump before the 3.12 freeze, so IMO we should backport this to 3.12. |
Sorry, something went wrong.
I'm not sure if I picked the wrong pkg-config package. But well, for now, my main worry is more to make the whole Python workflow more reliable by avoiding depending on the external quay.io server which had multiple outages in several days. With my change, the Python workflow no longer pulls an external container image, but simply reuse what's available on Ubuntu 22.04 in the GitHub Action.
Oh. So we cannot backport this change to 3.11? |
Sorry, something went wrong.
…H-112090) The "Check if generated files are up to date" job of GitHub Actions now runs the "autoreconf -ivf -Werror" command instead of the "make regen-configure" command to avoid depending on the external quay.io server. Add Tools/build/regen-configure.sh script to regenerate the configure with an Ubuntu container image. The "quay.io/tiran/cpython_autoconf:271" container image (https://github.com/tiran/cpython_autoconf) is no longer used. (cherry picked from commit d9fd33a) Co-authored-by: Victor Stinner <vstinner@python.org>
|
Merged. Thanks for reviews. Let's start with a backport to 3.12. |
Sorry, something went wrong.
No, 3.11 uses a patched Autoconf 2.69 from Alpine Linux, not a vanilla 2.69 installation. |
Sorry, something went wrong.
|
@vstinner I was doing some work on release-tools adjacent to this, @zware pointed me to this PR. What are your thoughts on backporting the regen-configure makefile target to all supported versions so that release-tools can depend on it being there? |
Sorry, something went wrong.
|
For 3.11 and earlier autoconf version configure generation udpates, ask the release managers (@pablogsal and @ambv) for those branches. (it makes sense for 3.12) |
Sorry, something went wrong.
…112090) The "Check if generated files are up to date" job of GitHub Actions now runs the "autoreconf -ivf -Werror" command instead of the "make regen-configure" command to avoid depending on the external quay.io server. Add Tools/build/regen-configure.sh script to regenerate the configure with an Ubuntu container image. The "quay.io/tiran/cpython_autoconf:271" container image (https://github.com/tiran/cpython_autoconf) is no longer used. (cherry picked from commit d9fd33a)
) (#112159) gh-112088: Run autoreconf in GHA check_generated_files (#112090) The "Check if generated files are up to date" job of GitHub Actions now runs the "autoreconf -ivf -Werror" command instead of the "make regen-configure" command to avoid depending on the external quay.io server. Add Tools/build/regen-configure.sh script to regenerate the configure with an Ubuntu container image. The "quay.io/tiran/cpython_autoconf:271" container image (https://github.com/tiran/cpython_autoconf) is no longer used. (cherry picked from commit d9fd33a)
…112090) The "Check if generated files are up to date" job of GitHub Actions now runs the "autoreconf -ivf -Werror" command instead of the "make regen-configure" command to avoid depending on the external quay.io server. Add Tools/build/regen-configure.sh script to regenerate the configure with an Ubuntu container image. The "quay.io/tiran/cpython_autoconf:271" container image (https://github.com/tiran/cpython_autoconf) is no longer used.
…112090) The "Check if generated files are up to date" job of GitHub Actions now runs the "autoreconf -ivf -Werror" command instead of the "make regen-configure" command to avoid depending on the external quay.io server. Add Tools/build/regen-configure.sh script to regenerate the configure with an Ubuntu container image. The "quay.io/tiran/cpython_autoconf:271" container image (https://github.com/tiran/cpython_autoconf) is no longer used.
|
I can see using of aclocal 1.16.5 in this PR. Should we provide some changes to docs for update them? |
Sorry, something went wrong.
Yes. Do you want to propose a PR to update the doc? |
Sorry, something went wrong.
Yes, I do. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
The "Check if generated files are up to date" job of GitHub Actions now runs the "autoreconf -ivf -Werror" command instead of the "make regen-configure" command to avoid depending on the unstable quay.io server.