[action] [PR:23694] Fix Debian repos used for Bullseye-based containers#1553
Merged
mssonicbld merged 1 commit intoAzure:202405from Aug 26, 2025
Merged
Conversation
Loading
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.
Why I did it
When building a Bullseye-based container with MIRROR_SNAPSHOT=y, the repos used will point to the main Debian repo, but Bullseye packages have been moved to the archive repo. Fix this issue by overriding the
DEFAULT_MIRROR_URLSvariable.Note that bullseye-security is still in the main Debian repo, and is not yet on the archive repo.
Work item tracking
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)