Repository navigation
Conversation
Debian 11 is end of life and deb.debian.org no longer serves its security pool, so building build-containers/Dockerfile.debian fails with 404s for libssl-dev, libssl1.1 and ca-certificates. That image backs the Linux glibc release prebuild and the CI package-artifact job. Point the bullseye sources at archive.debian.org so the image keeps building against glibc 2.31. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
6 of 11 tasks
This branch has not been deployed
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.
Summary
Debian 11 (bullseye) is end of life and
deb.debian.orgno longer serves its security pool, sobuild-containers/Dockerfile.debianstops building:That image backs the
linux-x64-glibcrelease prebuild and the CIPackage artifactjob. The last CI run onmainpredates the archive move, so it has not surfaced yet, but the next PR touchingbuild-containers/,lib/orsrc/, and the next release, would fail.This points the bullseye sources at
archive.debian.org(main, updates, security and backports, over HTTPS). The image keeps the glibc 2.31 baseline, so the produced prebuild is unchanged.Verification
npm run checknpm run native:check- not applicable; no native source changenpm run build- covered by the image build belownpm test- not applicable; no runtime or test changenpm run api:check- not applicable; no public API changenpm run types:check- not applicable; no type changenpm run e2e:chrome- not applicable; no browser interop path changenpm run wpt:selection:check- not applicablenpm run wpt:smoke- not applicablenpm run wpt:smoke:check- not applicablenpm run wpt:test/npm run wpt:check:strict- not applicableAdditionally:
linux/amd64linux/amd64andlinux/arm64(cmake 3.25.1 from bullseye-backports, glibc 2.31)Package artifactfails on an unchanged copy ofmain(https://github.com/pedrojhfs/webrtc/actions/runs/37539759758) and passes with this change (https://github.com/pedrojhfs/webrtc/actions/runs/37535904691, together with the arm64 branch built on top of it)WPT impact
None.
wpt-manifest.jsonanddocs/divergences.mdare unchanged.Browser interoperability
No Chrome E2E behavior or coverage changes.
Notes
No libdatachannel pin, WPT pin, native lifetime, callback-threading, permission, or publication impact. Release output is unchanged (same base image and glibc baseline); only the apt sources move to the archive.
🤖 Generated with Claude Code