[opensuse-factory] envoy-proxy and cilium-proxy
Hi, As many of you already know and were engaged in that - we have two packages related to Cilium and needed for Cilium container images - envoy-proxy and cilium-proxy. They are failing since some time due to Bazel being, let's say, a quite problematic build system for people who want to do packaging of C/C++ software properly and do not like downloading random stuff from Github during the build. Recently we aimed to fix those packages in the following Factory staging project: https://build.opensuse.org/project/show/openSUSE:Factory:Staging:adi:54 But the main submit request got rejected (which I don't mind and agree with): https://build.opensuse.org/request/show/744892 It's almost a week since the rejection and I finally managed to have green builds of cilium-proxy and envoy-proxy packages which do not bundle any dependencies. The project is here: https://build.opensuse.org/project/show/home:mrostecki:branches:devel:kubic The most important package here: https://build.opensuse.org/package/show/home:mrostecki:branches:devel:kubic/... As you can see, the home:mrostecki:branches:devel:kubic project has quite a lot of packages. Some of them are new, some of them are just modified packages which already exist in Factory or devel projects. We will most probably need to either: - add them all to adi:54 - start some new staging project when we will start everything from scratch @DimStar, @sysrich - WDYT? I will start creating submit requests to devel projects and Factory tomorrow and today I will just let all the stuff to rebuild on OBS - to be sure that I really did my job. I'm starting this email thread to share awarness of what I'm going to do tomorrow, coordinate the whole effort of fixing *-proxy packages and... hopefully... prove that I managed to solve the whole Bazel nightmare in the way acceptable for Linux distro packaging (although in future I will try to add some macros and try to make those specs less ugly). Cheers, Michal -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2019-11-07 17:54, Michal Rostecki wrote:
As you can see, the home:mrostecki:branches:devel:kubic project has quite a lot of packages. Some of them are new, some of them are just modified packages which already exist in Factory or devel projects.
We will most probably need to either:
- add them all to adi:54 - start some new staging project when we will start everything from scratch
IMHO the correct action is: - SR all the modified packages to the corresponding devel project - SR all the new packages to the most aligned devel project - For each package (new or present in a devel project), submit into Factory, or request the submition from the devel project - For each accepted change, remove it from your home, and adjust your meta in your home to find the removed package in the correct devel project - Iterate until your home is empty Basically this is your 2nd option, but without the need on an specific staging project, as your home will do the same job without requiring duplication. At least this is how I did this for similar issues. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Michal, On Thu, 2019-11-07 at 16:54 +0000, Michal Rostecki wrote:
Hi, … As you can see, the home:mrostecki:branches:devel:kubic project has quite a lot of packages. Some of them are new, some of them are just modified packages which already exist in Factory or devel projects.
Awesome to see this progress! Thanks for sharing.
We will most probably need to either:
- add them all to adi:54 - start some new staging project when we will start everything from scratch
There is a third option - especiall when we are talking about packages coming from multiple devel projects (and thus likely in very different speeds): * Let the staging bot group the incoming requests into adi different adi projects as they come along. Every package that is accepted counts immediately towards adi:54 (as adi:54 builds against openSUSE:Factory) If, at a time, we have all submissions ready, we can try to speed up things by merging stuff together into adi:54 (and chase up legal, as this will likely be the biggest bottleneck again here) Cheers, Dominique
An update about my efforts to fix envoy-proxy and cilium-proxy. For now I'm trying to solve two problems: - Both packages stopped to build successfully after the newest update of c-ares. The API of the ares_getaddrinfo changed a bit and I need to patch Envoy code to be compatible with it. Of course I will also submit a patch upstream. - I'm discussing with Jeff Kowalczyk how to handle Go module dependencies properly. Bazel requires Go modules to contain BUILD or BUILD.bazel files in their source trees which can be generated by a tool called bazel-gazelle.[0] I will try to use that tool to provide BUILD files for all golang-* packages which we need as dependencies for Envoy. We also need to cut off a release of golang-packaging which would contain my change which includes BUILD and WORKSPACE files in source trees.[1] Cheers, Michal [0] https://github.com/bazelbuild/bazel-gazelle [1] https://github.com/openSUSE/golang-packaging/commit/f7264573847504a530004661... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
The newest update. There are still two things to fix before envoy-proxy can become green in Factory. 1. We need to consume the newest snapshot of c-ares with git. Apparently, the tarballs available as "daily snapshots" on c-ares website[0] are not up to date and they don't contain fixes for getaddrinfo functionality which is needed for envoy-proxy to build. Adam Majer is checking whether consuming the newest commit will not break NodeJS builds. If not, then we will submit the newest git snapshot to Factory. 2. I need to fix golang-org-x-tools and golang-github-google-protobuf packages and apply `extras` patches from rules_go[1] project on them. Hopefully I will fix that today. [0] https://c-ares.haxx.se/daily-snapshot/ [1] https://github.com/bazelbuild/rules_go/tree/master/third_party -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
aplanas
-
Dominique Leuenberger / DimStar
-
Michal Rostecki