Skip to content

Bullseye has moved to the archive - #226

Merged
desrosj merged 3 commits into
trunkfrom
fix/debian-now-archived
Oct 22, 2026
Merged

desrosj merged 3 commits into
trunkfrom
fix/debian-now-archived

Conversation

@desrosj

@desrosj desrosj commented Sep 11, 2026 •

Copy link
Copy Markdown
Member

Debian 11 (bullseye) reached end of life on August 31, 2026, and has been moved to archive.debian.org. The PHP 7.4, 8.0, 8.1 and 8.2 images are built on bullseye, and they all began failing in the scheduled builds (e.g. this run). deb.debian.org still serves the bullseye-security index, but the package files are gone, so apt-get install fails with Err: on every package from the security suite.

Changes

For the four bullseye images, update.php now points both the main and security suites at the archive before running apt-get update.

This covers both deb.debian.org/debian (bullseye) and deb.debian.org/debian-security (bullseye-security). This follows the existing buster handling for PHP 7.2. The Dockerfiles were regenerated with php update.php.

archive.debian.org publishes both /debian/dists/bullseye and /debian-security/dists/bullseye-security, and neither Release file has a Valid-Until expiry. Keeping the security suite also means the images get the final bullseye security fixes, instead of shipping without two years of them.

Testing

  • All PHP and CLI image jobs pass in run 39638219478.
  • Some earlier attempts of that run failed because pecl.php.net was returning HTTP 500/504 errors (imagick and memcached downloads). That was unrelated to this change: 8.3–8.5 failed the same way. Rerunning once PECL recovered got everything green.

🤖 Generated with Claude Code

@desrosj desrosj self-assigned this Sep 11, 2026
desrosj and others added 2 commits October 21, 2026 12:49
Repoint both deb.debian.org/debian and deb.debian.org/debian-security to
archive.debian.org instead of deleting bullseye-security. Security fixes
published after the final point release only exist in the security suite,
and the newer 8.1 and 8.2 base images already have those versions
installed, so the matching -dev packages could not be installed without it.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@desrosj
desrosj marked this pull request as ready for review October 22, 2026 15:48
@github-actions

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: desrosj <desrosj@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

@desrosj

desrosj commented Oct 22, 2026

Copy link
Copy Markdown
Member Author

I'm going to merge this so that images can be rebuilt.

@desrosj
desrosj merged commit cfbf35f into trunk Oct 22, 2026
21 checks passed
@desrosj
desrosj deleted the fix/debian-now-archived branch October 22, 2026 15:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant