libyang: upgrade to v3 step 3 -- port sonic-yang-mgmt#21716
libyang: upgrade to v3 step 3 -- port sonic-yang-mgmt#21716bradh352 wants to merge 9 commits intosonic-net:masterfrom
Conversation
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@qiluo-msft @ganglyu this is the next PR in the series of libyang3 porting... |
4ba074f to
cb482c1
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
cb482c1 to
cf56243
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
491a041 to
ef2790d
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ef2790d to
5f82fd2
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
5f82fd2 to
2a4d521
Compare
|
Azure Pipelines successfully started running 1 pipeline(s). |
fb12c4e to
14dcadd
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
14dcadd to
4bafb2b
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
4bafb2b to
a329bb4
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
GCU calls this over and over. We don't want a whole tree reversal each time, cache!
a329bb4 to
df14eb9
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ce4f096 to
eb02b43
Compare
|
/azp run Azure.sonic-buildimage |
| $(LIBYANG3)_SRC_PATH = $(SRC_PATH)/libyang3 | ||
| SONIC_MAKE_DEBS += $(LIBYANG3) | ||
|
|
||
| LIBYANG3_DEV = libyang-dev_$(LIBYANG3_FULLVERSION)_$(CONFIGURED_ARCH).deb |
There was a problem hiding this comment.
Please rename to libyang3-dev_... to stick to existing naming convention
There was a problem hiding this comment.
The various versions of libyang's dev libraries conflict with eachother, this is likely why upstream debian named them the same. They cannot be installed simultaneously. Again, this is the upstream naming. It wouldn't be wise to change this and have to maintain patches for this purpose.
|
closing in favor of #26584 |
Why I did it
libyang3 porting. See master tracking ticket #22385
Port of sonic-yang-mgmt
NOTE: this PR actually includes (as a squashed commits) PR #21679, #21719. Please review the individual commits (skipping the squashed commit) otherwise this may seem too large/confusing.
Depends PR #21679, #21719
Fixes #22385
Work item tracking
How I did it
How to verify it
All PRs listed on #22385 must be merged into a local build tree in order to test due to cross-repository dependencies.
It is expected the CI/CD system to FAIL with this PR due to cross dependencies, so do not treat such failures as a reason to not review these changes.
Which release branch to backport (provide reason below if selected)
None
Tested branch (Please provide the tested image version)
master as of 20250212
Description for the changelog
libyang: upgrade to v3 step 2 -- port sonic-yang-mgmt
Link to config_db schema for YANG module changes
N/A
A picture of a cute animal (not mandatory but encouraged)
Signed-off-by: Brad House (@bradh352)