-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Convert docker-fpm-frr to buster #4920
Conversation
I believe we can avoid building our own swig and libyang for buster. |
patched libyang is required for mgmt-framework. |
@joyas-joseph what about swig? Can we use swig from the repo, and don't build it by ourselves? |
Let me take a look. |
retest broadcom please |
retest vs please |
retest broadcom please |
retest vs please |
retest broadcom please |
@joyas-joseph , can you rebase this pr to the latest master. |
7563ed5
to
04e20aa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As comments
fe01bee
retest vs please |
retest mellanox please |
https://packages.debian.org/buster/swig |
libyang was being compiled as a dependency for docker-sonic-vs which was using stretch environment and hence the use of 3.0.10 version of swig. |
retest mellanox please |
Are we going to use binary which is build under stretch with the binary which is building under buster? Is it safe? |
The way things are setup is that if we have a stretch docker that requires libyang, then it will be built in a stretch environment and that package will be used in the docker. At the same time, if we have a buster docker that requires libyang, then another libyang is built in buster environment and that package would be used. After the change to use swig from the distribution, we saw a build failure for 'vs' platform only. Build succeeded for other platforms. This was because 'vs' platform had 'docker-sonic-vs' which was a stretch docker and so libyang was being built for stretch. libyang requires at least 3.0.12 version but stretch had 3.0.10 version. Hence the failure. Now we have docker-sonic-vs converted to buster and so dont see a case of libyang being built for stretch. Hence the change to add back using swig from the distribution. |
retest mellanox please |
Thank you for detailed explanations @joyas-joseph ! |
it looks like mellanox build keeps failing at the same place. |
Not sure why |
bf3cdb5
e291815
to
bf3cdb5
Compare
Probably rules for |
Check .dep files. |
f93df89
to
879edf5
Compare
retest baseimage please |
#5039 should solve the mellanox build failure. |
Signed-off-by: Joyas Joseph <joyas_joseph@dell.com>
Signed-off-by: Joyas Joseph <joyas_joseph@dell.com>
879edf5
to
eb25e9b
Compare
retest vsimage please |
retest broadcom please |
1 similar comment
retest broadcom please |
retest vsimage please |
retest mellanox please |
Signed-off-by: Joyas Joseph joyas_joseph@dell.com
- Why I did it
This is an enhancement.
- How I did it
Code change
- How to verify it
Build
target/docker-fpm-frr.gz
Verify that
/etc/apt/sources.list
points tobuster
usingdocker exec bgp cat /etc/apt/sources.list
BGP neighborship is established.
- Description for the changelog
Convert docker-fpm-frr to buster
- A picture of a cute animal (not mandatory but encouraged)