Skip to content

ci: migrate libyang1 deb install to libyang3#693

Merged
vaibhavhd merged 1 commit into
sonic-net:masterfrom
bhouse-nexthop:bhouse.libyang3-debs
Jun 3, 2026
Merged

ci: migrate libyang1 deb install to libyang3#693
vaibhavhd merged 1 commit into
sonic-net:masterfrom
bhouse-nexthop:bhouse.libyang3-debs

Conversation

@bhouse-nexthop
Copy link
Copy Markdown
Contributor

Why I did it

sonic-buildimage no longer builds the libyang1 debs (libyang_1.0.73, libyang-cpp, python3-yang); it now builds only libyang3. The sonic-gnmi CI downloads and installs libyang debs from the sonic-buildimage.common_libs build artifact, and the libyang1-versioned download patterns no longer match any produced artifact, which would break the dependency-install step.

How I did it

Updated the libyang download filter list in .azure/templates/install-dependencies.yml:

  • Removed target/debs/trixie/libyang_1.0*.deb (the v1 runtime library); the libyang3 runtime is already covered by the existing target/debs/trixie/libyang3_*.deb pattern.
  • Replaced target/debs/trixie/libyang-*_1.0*.deb (which matched the now-removed libyang-cpp and the v1 libyang-dev) with the versionless target/debs/trixie/libyang-dev_*.deb (now v3), dropping libyang-cpp entirely.

All patterns are versionless globs. The install step already uses a generic find ... -name '*.deb' invocation, so it installs whatever was downloaded and needed no change.

Left unchanged:

  • doc/telemetry-dev-env/Dockerfile builds libyang 1.0.184 from CESNET source for the developer environment; it is not a sonic-buildimage build asset.
  • Makefile comments referencing libyang memory leaks are descriptive only and unrelated to the deb migration.

How to verify it

  • Run the sonic-gnmi Azure CI; the "Download libyang and libnl from common_libs" step resolves the new versionless libyang3 patterns, and the "Install libyang and libnl debs" step installs them successfully.
  • Confirm no remaining libyang1 deb references or hardcoded versions: grep -rnI 'libyang_1.0\|libyang-.*_1.0' .azure/

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111

Description for the changelog

ci: migrate libyang1 deb install to libyang3 (part of sonic-net/sonic-buildimage#22385)

Link to config_db schema for YANG module changes

N/A

@mssonicbld
Copy link
Copy Markdown
Contributor

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

sonic-buildimage no longer builds the libyang1 debs (libyang_1.0.73,
libyang-cpp, python3-yang); it now builds only libyang3. Update the
libyang download filter list in .azure/templates/install-dependencies.yml
to use versionless libyang3 globs: drop libyang_1.0*.deb (covered by the
existing libyang3_*.deb pattern) and replace libyang-*_1.0*.deb (which
matched libyang-cpp and v1 libyang-dev) with libyang-dev_*.deb, dropping
libyang-cpp entirely. The install step uses a generic *.deb find and
needs no change.

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

Signed-off-by: Brad House <bhouse@nexthop.ai>
@bhouse-nexthop bhouse-nexthop force-pushed the bhouse.libyang3-debs branch from f104ab1 to 1fb82bb Compare May 31, 2026 14:38
@mssonicbld
Copy link
Copy Markdown
Contributor

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@rookie-who
Copy link
Copy Markdown
Contributor

/azp run

@azure-pipelines
Copy link
Copy Markdown

Commenter does not have sufficient privileges for PR 693 in repo sonic-net/sonic-gnmi

Copy link
Copy Markdown
Contributor

@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 — libyang1 download patterns removed, libyang3 equivalents in place.

@vaibhavhd
Copy link
Copy Markdown

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@vaibhavhd vaibhavhd merged commit dd99be1 into sonic-net:master Jun 3, 2026
13 checks passed
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.

4 participants