[action] [PR:82] azure-pipelines: migrate libyang1 deb install to libyang3#84
Merged
Merged
Conversation
#### Why I did it `sonic-buildimage` no longer builds the legacy libyang1 packages (`libyang_1.0.73`, `libyang-cpp`, `python3-yang`) — the build now produces only libyang3 (`libyang3`, `python3-libyang`). This repo's CI still `dpkg -i`'s the libyang1 deb, which will fail once libyang1 is gone. Part of the libyang3 migration tracked in sonic-net/sonic-buildimage#22385. #### How I did it Updated the `azure-pipelines.yml` dependency install step to install the libyang3 deb using a versionless glob (`libyang3_*.deb`) instead of `libyang_1.*.deb`. #### How to verify it CI install step succeeds against the libyang3 debs produced by current `sonic-buildimage` master. #### Description for the changelog azure-pipelines: install libyang3 instead of libyang1. Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
Author
|
Original PR: #82 |
Author
|
/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
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 packages (libyang_1.0.73,libyang-cpp,python3-yang) — the build now produces only libyang3 (libyang3,python3-libyang). This repo's CI stilldpkg -i's the libyang1 deb, which will fail once libyang1 is gone.Part of the libyang3 migration tracked in sonic-net/sonic-buildimage#22385.
How I did it
Updated the
azure-pipelines.ymldependency install step to install the libyang3 deb using a versionless glob (libyang3_*.deb) instead oflibyang_1.*.deb.How to verify it
CI install step succeeds against the libyang3 debs produced by current
sonic-buildimagemaster.Description for the changelog
azure-pipelines: install libyang3 instead of libyang1.
Signed-off-by: Sonic Build Admin sonicbld@microsoft.com