Repository navigation
[9.5](backport #7782) fix: bypass expired Debian 11 security repo in Dockerfile.build - #7786
Closed
mergify[bot] wants to merge 1 commit into
Closed
mergify[bot] wants to merge 1 commit into
mergify[bot] wants to merge 1 commit into
Conversation
Temporary workaround for the Buildkite package build failures caused by the Debian 11 (Bullseye) security repository's InRelease file expiring after EOL. The root cause fix is upstream in golang-crossbuild: elastic/golang-crossbuild#754 Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> (cherry picked from commit bc44a05)
mergify
Bot
requested review from
macdewee and
ycombinator
and removed request for
a team
September 9, 2026 07:20
4 tasks done
Contributor
|
Closing unmerged as |
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
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 is the problem this PR solves?
The Buildkite
Package x86_64andPackage aarch64jobs are failing (e.g. build #16689) because Debian 11 (Bullseye) reached EOL and its security repository'sInReleasefile has expired.apt-get updateinDockerfile.buildfails with:The root cause fix is in the upstream base image: elastic/golang-crossbuild#754, which switches Debian 11 sources to the archive and snapshot mirrors. This PR should be reverted once that PR is merged and new
golang-crossbuildimages are published.How does this PR solve the problem?
Passes
-o Acquire::Check-Valid-Until=falsetoapt-get updateinDockerfile.buildto bypass the expiry check. This does not change the Debian version being built for — the base image remainsgolang-crossbuild:*-debian11. Since Debian 11 is EOL, the security repo has no new updates regardless, so bypassing the validity check has no practical security impact.How to test this PR locally
Trigger a packaging build or run locally:
Design Checklist
Checklist
Related issues
This is an automatic backport of pull request fix: bypass expired Debian 11 security repo in Dockerfile.build #7782 done by Mergify.