Repair wp/7.0 branch Actions: Fix wp-env Docker builds broken by archived Debian Bullseye repositories - #263
Closed
desrosj wants to merge 1 commit into
Conversation
desrosj
added this pull request to stack #179
September 11, 2026 15:23
desrosj
force-pushed
the
fix-actions-7.0/fix-wp-env-debian-bullseye
branch
from
September 11, 2026 17:04
7916454 to
00bc561
Compare
desrosj
marked this pull request as ready for review
September 11, 2026 18:17
|
Warning: Type of PR label mismatch To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.
Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task. |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Cherry-picks d21304e (WordPress#82478) into the `wp/7.0` branch to fix failures encountered when attempting to use a version of PHP that relies on Debian Bullseye. Debian 11 ("bullseye") reached end-of-life on 2026-08-31 and its packages left the regular mirrors. Since then, `wp-env start`'s Docker build for the bullseye-based WordPress images fails during `apt-get -qy install sudo` with 404s against `deb.debian.org`. This branch supports PHP 7.4, 8.0, 8.1, and 8.2 within its wider support window, which fall within the bullseye-affected range, so the same class of fix already applied for Debian Stretch/Buster on this branch is needed here for Bullseye too: point the `bullseye` apt suite at `archive.debian.org`, dropping the `bullseye-security`/`bullseye-updates` suites entirely (rather than rewriting them) since `archive.debian.org` doesn't carry `bullseye-security` yet.
desrosj
force-pushed
the
fix-actions-7.0/fix-wp-env-debian-bullseye
branch
from
September 11, 2026 18:38
00bc561 to
c6228c0
Compare
|
Size Change: 0 B Total Size: 7.61 MB ℹ️ View Unchanged
|
Owner
Author
|
Migrated to real upstream: WordPress#82808. Closing this fork PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Cherry-picks upstream trunk commit
d21304e3323571401364805242fc26d1cf03a52d(#82478) into this branch'swp-envpackage source (packages/env/lib/runtime/docker/init-config.js) to fixwp-envDocker build failures caused by the Debian Bullseye repositories being archived after Debian 11 reached end-of-life.Why?
Debian moves a release's package repositories to its archive server once that release reaches end-of-life.
wp-env start's Docker build fails withapt-get404s against the regular mirrors for any PHP version whose base image relies on the now-archived Bullseye release. This branch supports PHP 7.4, 8.0, 8.1, and 8.2 within its wider support window, which fall in the affected range, so the fix is needed even though this branch's CI may not actively test every affected PHP version — a contributor could still usewp-envlocally with any officially supported version.Use of AI Tools
This PR was authored with the help of Claude Code.