-
Notifications
You must be signed in to change notification settings - Fork 322
[azp] Only grab libyang v1 libs for AZP jobs #1031
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Lawrence Lee <[email protected]>
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Lawrence Lee <[email protected]>
Signed-off-by: Lawrence Lee <[email protected]>
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Since this PR only fix build steps, the vstest failure is not relevant, and tracked by below items: This PR is needed in the DVS image to fix the test issue: [trim]: Add Packet Trimming Asym DSCP to VS lib by nazariig · Pull Request #1610 · sonic-net/sonic-sairedis However, the sairedis submodule update was blocked until a few minutes ago ([submodule][master] Update submodule sonic-sairedis to the latest HEAD automatically by mssonicbld · Pull Request #23215 · sonic-net/sonic-buildimage). I will merge this PR. |
|
Cherry-pick PR to msft-202506: Azure/sonic-swss-common.msft#46 |
Limit grabbed libyang libraries to only v1.
Upgrading to libyang v3 (sonic-net/sonic-buildimage#21679) is causing the swss-common pipeline build to fail. The pipeline assumes that any package starting with
libyang_orlibyang-is a libyang v1 package and tries to install it. However, the dev header package for libyang v3 starts withlibyang-, so the pipeline tries to download/install it as well, which causes the build to fail since it depends on the base libyang v3 package which is not grabbed because it starts withlibyang3.