azure-pipelines: migrate libyang1 deb install to libyang3#37
Open
bhouse-nexthop wants to merge 1 commit into
Open
azure-pipelines: migrate libyang1 deb install to libyang3#37bhouse-nexthop wants to merge 1 commit into
bhouse-nexthop wants to merge 1 commit into
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sonic-buildimage no longer builds the libyang1 debs (libyang_1.0.73, libyang-cpp, python3-yang) and now builds only libyang3. Update the bookworm dependency install step to install the libyang3 runtime deb using a versionless glob instead of the removed libyang 1.0.73 deb. The download pattern target/debs/bookworm/libyang*.deb already matches the libyang3 artifacts, so only the dpkg install line needed changing. Part of sonic-net/sonic-buildimage#22385. Signed-off-by: Brad House <bhouse@nexthop.ai>
bhouse-nexthop
force-pushed
the
bhouse.libyang3-debs
branch
from
96971c6 to
8f7cb6c
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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 migration.
vaibhavhd
approved these changes
Jun 3, 2026
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-buildimageno longer builds the libyang1 debs (libyang_1.0.73,libyang-cpp,python3-yang); it now builds only libyang3. Thesonic-bmpAzure pipeline installed the removedlibyang*1.0.73*.debfrom the downloadedsonic-buildimagebuild assets, so the dependency install step would fail to find/install that file.Part of sonic-net/sonic-buildimage#22385.
Work item tracking
How I did it
Updated the
Install libswsscommon dependenciesstep inazure-pipelines.ymlto install the libyang3 runtime deb using a versionless glob (libyang3_*.deb) instead of the removedlibyang*1.0.73*.deb. The existing download patterntarget/debs/bookworm/libyang*.debalready matches the libyang3 artifacts, so no change was needed there. Only the runtime library is required here (the prebuiltsonic-swss-commondeb links libyang at runtime), so no-dev/headers package is installed.How to verify it
Run the Azure pipeline; the
Download bookworm debsstep pulls the libyang3 deb via the existing glob, and theInstall libswsscommon dependenciesstep installslibyang3_*.debsuccessfully.Which release branch to backport (provide reason below if selected)
Tested branch (Add it nightly build branch here)
Description for the changelog
azure-pipelines: migrate libyang1 deb install to libyang3
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)