azure-pipelines: install libyang3 instead of libyang1#386
Open
bhouse-nexthop wants to merge 1 commit into
Open
azure-pipelines: install libyang3 instead of libyang1#386bhouse-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). It now builds only libyang3. Update the CI dependency install step to install the versionless libyang3 deb glob instead of the removed libyang1 deb. Part of sonic-net/sonic-buildimage#22385. Signed-off-by: Brad House <bhouse@nexthop.ai>
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Commenter does not have sufficient privileges for PR 386 in repo sonic-net/sonic-host-services |
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 — clean libyang1 → libyang3 replacement.
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
vaibhavhd
approved these changes
Jun 3, 2026
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Why I did it
sonic-buildimage no longer builds the libyang1 Debian packages (
libyang_1.0.73,libyang-cpp,python3-yang); it now builds only libyang3. The CI pipeline here installslibyang_1.0.73_*.debfrom the downloaded sonic-buildimage build artifacts, which no longer exist, so the dependency install step would fail.Part of sonic-net/sonic-buildimage#22385.
How I did it
Updated
azure-pipelines.ymlto install the libyang3 deb using a versionless glob instead of the removed libyang1 deb:sudo dpkg -i libyang_1.0.73_*.deb→sudo dpkg -i libyang3_*.debNo
libyang-cpp,python3-yang, orlibyang-devreferences exist in this repository, so no other changes were needed.How to verify it
Run the Azure pipeline (or the "Install Debian dependencies" step) against artifacts from a current sonic-buildimage build. The
libyang3_*.debglob resolves to the libyang3 package produced by sonic-buildimage and installs successfully, where the oldlibyang_1.0.73_*.debglob would match nothing.Description for the changelog
azure-pipelines: install libyang3 instead of libyang1