azure-pipelines: migrate libyang1 deb install to libyang3#341
Open
bhouse-nexthop wants to merge 1 commit into
Open
azure-pipelines: migrate libyang1 deb install to libyang3#341bhouse-nexthop wants to merge 1 commit into
bhouse-nexthop wants to merge 1 commit into
Conversation
sonic-buildimage no longer builds the libyang1 debs (libyang_1.0.73, libyang-cpp, python3-yang); the common_libs pipeline now produces only libyang3. Update the common-lib artifact download patterns to fetch the libyang3 deb instead of the removed libyang_*.deb, using a versionless glob. The install step uses a generic find for *.deb and needs no change. Part of sonic-net/sonic-buildimage#22385. Signed-off-by: Brad House <bhouse@nexthop.ai>
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Commenter does not have sufficient privileges for PR 341 in repo sonic-net/sonic-linkmgrd |
rookie-who
approved these changes
Jun 3, 2026
rookie-who
left a comment
rookie-who
left a comment
There was a problem hiding this comment.
LGTM — download patterns correctly updated across all three arch targets.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
vaibhavhd
approved these changes
Jun 3, 2026
Author
|
/azpw run |
Collaborator
|
Retrying failed(or canceled) jobs... |
Collaborator
|
No failed(or canceled) stages or jobs found in the most recent build 1129408. |
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
4 participants
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.
Description of PR
Summary:
sonic-buildimageno longer builds the legacy libyang1 deb (libyang_1.0.73); it now builds only libyang3. Updated the threeDownloadPipelineArtifactfilter patterns inazure-pipelines.ymlfromtarget/debs/bookworm/libyang_*.debtotarget/debs/bookworm/libyang3_*.debso CI pulls the libyang3 deb. The install steps use a genericdpkg -i $(find ./download -name *.deb), so no install-command change was needed.Part of sonic-net/sonic-buildimage#22385.
Fixes # (N/A — tracked under sonic-net/sonic-buildimage#22385)
Type of change
Approach
What is the motivation for this PR?
Once libyang1 is removed from
sonic-buildimage, the oldlibyang_*.debdownload filter matches nothing and CI fails to install libyang.Work item tracking
How did you do it?
Replaced
libyang_*.debwithlibyang3_*.debin all three artifact-download filters (amd64 / arm64 / armhf common-lib).How did you verify/test it?
Re-grepped for libyang1 references — none remain except the CodeQL/LGTM distro-apt
libyang-deventries (not sourced fromsonic-buildimageartifacts), which were intentionally left unchanged.Any platform specific information?
None.
Documentation
No documentation changes required.