Skip to content

azure-pipelines: migrate libyang1 deb install to libyang3#82

Open
bhouse-nexthop wants to merge 1 commit into
sonic-net:masterfrom
bhouse-nexthop:bhouse.libyang3-debs
Open

azure-pipelines: migrate libyang1 deb install to libyang3#82
bhouse-nexthop wants to merge 1 commit into
sonic-net:masterfrom
bhouse-nexthop:bhouse.libyang3-debs

Conversation

@bhouse-nexthop
Copy link
Copy Markdown

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.

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>
@mssonicbld
Copy link
Copy Markdown

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants