-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[master] debian buster-backports does not have a Release file. #18679
Comments
If I change the source list of |
#18678 can help fix. buster-backports is removed recently. |
Very useful. Thanks a lot. |
@liushilongbuaa Kindly assist me to resolve this issue, I'm getting the following error while running workaround configure command: => => transferring context: 2B 0.0s
|
Your comment format is too bad. It seems that you didn't paste the fatal error. It locates a few lines upper. |
@liushilongbuaa |
Oh, This walk around is not good. How about 'SONIC_VERSION_CONTROL_COMPONENTS=deb'? |
Please try make configure PLATFORM=vs SONIC_VERSION_CONTROL_COMPONENTS=deb |
I'm seeing something odd when using the patch from #18678, the wrong sources.list file is being picked up for one of the docker steps when building Build command: Logs:
|
@liushilongbuaa @saiarcot895 I have taken the patch to 202311 branch, but still can see the failure, would you please help to check?
|
Hi @oplklum , Can you please let me know in which file did you make this change? Thanks in advance |
This only works for base image. Please don't use cache on docker-base-buster |
Hi @SaranyaAzhgamuthaiyan, sorry for the late reply. This is a temporary change. My change steps are shown below:
|
Description
I cloned the latest sonic buildimage code and built sonic on a new machine. There was a error reported "E: The repository 'http://debian-archive.trafficmanager.net/debian buster-backports Release" does not have a Release file." when I executed "make configure PLATFORM=vs". So I think this is an outdated repository for buster-backports. Would someone please have look at this problem?
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: