azure-pipelines: migrate libyang1 deb install to libyang3#82
azure-pipelines: migrate libyang1 deb install to libyang3#82bhouse-nexthop wants to merge 1 commit into
Conversation
The libyang1 debs (libyang_1.0.73) are no longer built by sonic-buildimage; the build now produces only libyang3. Update the dependency install step to pull the libyang3 deb (versionless glob) so CI keeps working after libyang1 is removed. 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 82 in repo sonic-net/sonic-dbsyncd |
rookie-who
left a comment
rookie-who
left a comment
There was a problem hiding this comment.
LGTM — clean mechanical replacement of libyang1 with libyang3 deb in CI pipeline.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run |
|
Retrying failed(or canceled) jobs... |
|
Retrying failed(or canceled) stages in build 1129397: ✅Stage __default: |
|
/azpw run |
|
Retrying failed(or canceled) jobs... |
|
Retrying failed(or canceled) stages in build 1129397: ✅Stage __default: |
4 participants
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.