libyang3: install libyang3 debs instead of libyang1#189
Open
bhouse-nexthop wants to merge 1 commit into
Open
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This was referenced May 31, 2026
sonic-buildimage no longer builds the libyang1 debs (libyang_1.0.73, libyang-cpp, python3-yang); it now builds only libyang3. - Dockerfile.common.prod: install the libyang3 runtime deb via a versionless glob (libyang3_*.deb). - copy.sh / dependencies.conf: the sonic-build artifacts API requires an exact filename (wildcards are not resolved), so these name the concrete libyang3 deb (libyang3_3.12.2-1), consistent with every other pinned dependency in these files. copy.sh also moves the libyang fetch to the bookworm path, since libyang3 is not built for buster. 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
d55bbdc to
f6604b1
Compare
|
/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
2 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 legacy libyang1 debs (libyang_1.0.73,libyang-cpp,python3-yang); it now builds only libyang3 (libyang3,python3-libyang). The prebuilt-deb references here would break once libyang1 is gone.Part of the libyang3 migration tracked in sonic-net/sonic-buildimage#22385.
How I did it
Dockerfile.common.prod— install the libyang3 runtime deb from/debsvia a versionless glob (libyang3_*.deb).copy.sh/dependencies.conf— thesonic-buildartifacts API requires an exact artifact filename (wildcardtarget=does not resolve), so these name the concretelibyang3_3.12.2-1deb, consistent with every other version-pinned dependency in these files.copy.shalso moves the libyang fetch to thebookwormartifact path, since libyang3 is not built forbuster.These pinned references will need a bump when libyang3's version changes — exactly as the other pinned debs in these files already do; only the Dockerfile install uses a versionless glob.
How to verify it
libyang3_3.12.2-1_amd64.debis published on currentsonic-buildimagemaster (bookworm) and downloads via the artifacts API; the Docker build installs it through the/debs/libyang3_*.debglob.Description for the changelog
libyang3: install libyang3 instead of libyang1 (Dockerfile glob + version-pinned artifact references).