Skip to content

azure-pipelines: install only libyang3 (drop libyang1)#683

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

azure-pipelines: install only libyang3 (drop libyang1)#683
bhouse-nexthop wants to merge 1 commit into
sonic-net:masterfrom
bhouse-nexthop:bhouse.libyang3-debs

Conversation

@bhouse-nexthop
Copy link
Copy Markdown

Description

Update the CI pipeline to install only the libyang3 Debian packages and drop the libyang1 packages. sonic-buildimage no longer builds libyang1 (libyang_1.0.73); it now builds only libyang3, so the libyang1 download filter and install command no longer resolve to any artifact. The libyang3 packages (libyang3_*.deb, python3-libyang*.deb) were already added during the transition (#589) and remain in place using versionless globs.

Motivation and Context

sonic-buildimage stopped building the libyang1 packages (libyang_1.0.73, libyang-cpp, python3-yang) and now builds only libyang3 (see sonic-net/sonic-buildimage#22385). A prior change (#589) installed both libyang1 and libyang3 during the transition. With libyang1 gone, the target/debs/trixie/libyang_1.0.73_amd64.deb download filter and the sudo dpkg -i libyang_1.0.73_amd64.deb install step reference an artifact that no longer exists, which would break the pipeline. This change removes those libyang1 references and keeps only the libyang3 globs.

How Has This Been Tested?

Verified that after the change azure-pipelines.yml no longer references the libyang1 package and only references libyang3 packages via versionless globs (libyang3_*.deb, python3-libyang*.deb). The Debian dependency download and install steps continue to resolve against the libyang3 artifacts produced by current sonic-buildimage builds.

Additional Information (Optional)

Part of sonic-net/sonic-buildimage#22385.

sonic-buildimage no longer builds the libyang1 debs (libyang_1.0.73,
libyang-cpp, python3-yang); it now builds only libyang3. Remove the
hardcoded libyang_1.0.73_amd64.deb from the dpkg install and keep only
the versionless libyang3_*.deb and python3-libyang*.deb globs.

Part of sonic-net/sonic-buildimage#22385.

Signed-off-by: Brad House <bhouse@nexthop.ai>
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@lguohan
Copy link
Copy Markdown
Contributor

lguohan commented Jun 1, 2026

@bhouse-nexthop , can you check why the build failed?

@bhouse-nexthop
Copy link
Copy Markdown
Author

this failed because sonic-net/sonic-mgmt-common#157 and sonic-net/sonic-buildimage#27629 must merge first, plus have enough time for the build assets it pulls to be updated. Then this will pass.

@rookie-who
Copy link
Copy Markdown

/azp run

@azure-pipelines
Copy link
Copy Markdown

Commenter does not have sufficient privileges for PR 683 in repo sonic-net/sonic-platform-common

Copy link
Copy Markdown

@rookie-who rookie-who left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — clean removal of redundant libyang1, libyang3 already in place.

@vaibhavhd
Copy link
Copy Markdown

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@vaibhavhd
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.

5 participants