azure-pipelines: migrate libyang1 deb install to libyang3#161
Merged
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
sonic-buildimage no longer builds the libyang 1.0.73 debs (libyang, libyang-cpp, python3-yang); it now builds only libyang3. Update the pipeline to download and install the libyang3 debs using versionless globs: - download/install libyang3_*.deb and libyang-dev_*.deb (replacing the versioned libyang*1.0.73* set) - python3-yang_*.deb -> python3-libyang_*.deb - drop the removed libyang-cpp deb - generalize the LIBPCRE3 comment to reference libyang3 Part of sonic-net/sonic-buildimage#22385. Signed-off-by: Brad House <bhouse@nexthop.ai>
bhouse-nexthop
force-pushed
the
bhouse.libyang3-debs
branch
from
d0f1530 to
02214d7
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Commenter does not have sufficient privileges for PR 161 in repo sonic-net/sonic-mgmt-framework |
rookie-who
approved these changes
Jun 3, 2026
rookie-who
left a comment
rookie-who
left a comment
There was a problem hiding this comment.
LGTM — good improvement switching from overly broad libyang*.deb glob to explicit libyang3 patterns.
vaibhavhd
approved these changes
Jun 3, 2026
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
eduardoterto
added a commit
to terto-networks/sonic-mgmt-framework
that referenced
this pull request
Jun 16, 2026
* azure-pipelines: migrate libyang1 deb install to libyang3 (sonic-net#161) sonic-buildimage no longer builds the libyang 1.0.73 debs (libyang, libyang-cpp, python3-yang); it now builds only libyang3. Update the pipeline to download and install the libyang3 debs using versionless globs: - download/install libyang3_*.deb and libyang-dev_*.deb (replacing the versioned libyang*1.0.73* set) - python3-yang_*.deb -> python3-libyang_*.deb - drop the removed libyang-cpp deb - generalize the LIBPCRE3 comment to reference libyang3 Part of sonic-net/sonic-buildimage#22385. Signed-off-by: Brad House <bhouse@nexthop.ai> * feat(klish): mtr/nslookup/dig/host na privileged-view (espelhando exec) PR #22 adicionou esses comandos so' na exec-view (user mode `>`). Operador no `enable` (`#`) nao tem acesso — ping/traceroute estao DUPLICADOS no privileged-view, entao mtr/etc precisam do mesmo. Bug descoberto smoke fresh v0.7.18 final. --------- Signed-off-by: Brad House <bhouse@nexthop.ai> Co-authored-by: Brad House - Nexthop <bhouse@nexthop.ai>
eduardoterto
added a commit
to terto-networks/sonic-mgmt-framework
that referenced
this pull request
Jun 16, 2026
* azure-pipelines: migrate libyang1 deb install to libyang3 (sonic-net#161) sonic-buildimage no longer builds the libyang 1.0.73 debs (libyang, libyang-cpp, python3-yang); it now builds only libyang3. Update the pipeline to download and install the libyang3 debs using versionless globs: - download/install libyang3_*.deb and libyang-dev_*.deb (replacing the versioned libyang*1.0.73* set) - python3-yang_*.deb -> python3-libyang_*.deb - drop the removed libyang-cpp deb - generalize the LIBPCRE3 comment to reference libyang3 Part of sonic-net/sonic-buildimage#22385. Signed-off-by: Brad House <bhouse@nexthop.ai> * feat(klish): Top-5 ROI gap fixes 1. BGP one-liner neighbor X remote-as Y (config-router-bgp-view) + neighbor update-source/description/peer-group atalhos. Antes precisava entrar em config-router-bgp-nbr-view aninhado. 2. show ip bgp summary/neighbors, show bgp ipv4 vpn, show bgp l2vpn evpn, show evpn vni/mac/arp-cache/es, show l2vpn atom vc/binding, show isis neighbor/database/interface/route, show sr-te policy. Wrappers vtysh estruturados (operador nao precisa cair em bash). 3. Sweep SUBCOMMAND value="<kw>" em isis (af unicast), qos (traffic-class, queue, pg), interface (wred-profile, scheduler, profile), l2vpn (pw-id). Bug documentado em project_klish_subcommand_value_fix. --------- Signed-off-by: Brad House <bhouse@nexthop.ai> Co-authored-by: Brad House - Nexthop <bhouse@nexthop.ai>
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
5 participants
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-buildimage no longer builds the libyang 1.0.73 debs (
libyang,libyang-cpp,python3-yang); it now builds only libyang3. The CI pipeline still downloads and installs the removed libyang1 debs from the sonic-buildimage build artifacts, so it must switch to the libyang3 debs.Part of sonic-net/sonic-buildimage#22385.
How I did it
Updated
azure-pipelines.ymlto consume the libyang3 debs using versionless globs:libyang3_*.debandlibyang-dev_*.debin place of the versionedlibyang*1.0.73*set.python3-yang_*.debtopython3-libyang_*.deb.libyang-cppdeb.LIBPCRE3comment that referencedlibyang 1.0.73to referencelibyang3.How to verify it
azure-pipelines.ymlbuild and confirm the download step pulls the libyang3 debs from the sonic-buildimage artifacts anddpkg -iinstalls them without error.Description for the changelog
azure-pipelines: migrate libyang1 deb install to libyang3