Skip to content

Update build pipeline to build for Bullseye#1225

Merged
saiarcot895 merged 4 commits intosonic-net:masterfrom
saiarcot895:bullseye-docker-sonic-vs
Mar 30, 2023
Merged

Update build pipeline to build for Bullseye#1225
saiarcot895 merged 4 commits intosonic-net:masterfrom
saiarcot895:bullseye-docker-sonic-vs

Conversation

@saiarcot895
Copy link
Contributor

With the merge of sonic-net/sonic-buildimage#13294, docker-sonic-vs is now based on Bullseye. Switch to building for Bullseye to match that change.

With the merge of sonic-net/sonic-buildimage#13294, docker-sonic-vs is
now based on Bullseye. Switch to building for Bullseye to match that
change.

Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
@saiarcot895
Copy link
Contributor Author

/azp run Azure.sonic-sairedis

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
@saiarcot895 saiarcot895 merged commit 60fa682 into sonic-net:master Mar 30, 2023
saiarcot895 added a commit to saiarcot895/sonic-sairedis that referenced this pull request Jul 30, 2023
PR sonic-net#1225 removed a step where existing deb packages were removed before
installing the new deb packages. The problem is that due to Docker's
change detection code, where it only checks the file size and the
modification timestamp, even if the file gets modified when installing a
newer debian package, the file size may remain the same, and the
modification timestamp will remain the same (since this is based on the
debian/changelog timestamp). This caused changed binaries to not
actually replace the existing binaries.

Fix this by re-adding the line that removed existing packages first.

Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
xumia pushed a commit that referenced this pull request Jul 31, 2023
…1269)

PR #1225 removed a step where existing deb packages were removed before
installing the new deb packages. The problem is that due to Docker's
change detection code, where it only checks the file size and the
modification timestamp, even if the file gets modified when installing a
newer debian package, the file size may remain the same, and the
modification timestamp will remain the same (since this is based on the
debian/changelog timestamp). This caused changed binaries to not
actually replace the existing binaries.

Fix this by re-adding the line that removed existing packages first.

Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
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.

3 participants