dist: Add debian packaging

[phlax]

Commit Message: dist: Add debian packaging
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

[repokitteh-read-only]

CC @envoyproxy/dependency-shepherds: Your approval is needed for changes made to (bazel/.*repos.*\.bzl)|(bazel/dependency_imports\.bzl)|(api/bazel/.*\.bzl)|(.*/requirements\.txt)|(.*\.patch).

🐱

Caused by: #17979 was opened by phlax.

see: more, trace.

[phlax]

Might still be worth checking out if there is an actual aarch64-linux-gnu-gcc available in your build container in case some other library of yours actually needs it.

re this - see this commit - https://github.com/envoyproxy/envoy-build-tools/pull/166/files#diff-de88d82423c82fcf8e66cf5d50f69b4de3ca587502583ffa1fdd0c48b504cadeR162-R163 - altho im a bit baffled why its not working

atm, rules_python doesnt have good support for cython on mac - and non-precompiled-but-needs-to-be packages on arm are best avoided - even if they can be made to work they often add a lot of build time

that said - it would be good to know why this hasnt worked - altho wrt to the psutil dep, the case for keeping it was too weak to justify spending any time on it

re arm on docker - i think qemu is probs the easiest way to test on an x86 machine (see eg https://www.stereolabs.com/docs/docker/building-arm-container-on-x86/)

[MarkusTeufelberger]

A lot of your build process for that image was/is cached. I'm not 100% up-to-date on when Docker would actually rebuild something, but I assume that since the Dockerfile itself didn't change, you might actually have some rather unexpected things in those build containers... Another option would be that sourcing this other file caused the shell to close earlier than expected, but I'm also not 100% on that one.

Yes, I know about QEMU, but debugging ARM64 build containers for bazel is a few hops too far into that specific rabbit hole, sorry.

[phlax]

debugging ARM64 build containers for bazel is a few hops too far into that specific rabbit hole,

yep, my thought too - hence the easier path of just removing the problem dep

[phlax]

re the docker build - the artefacts/context changed so that would cause a rebuild - not sure that there is caching going on in the envoy-build-tools build - so i think it rebuilds all on every run regardless

if it hadnt rebuilt theres a bunch of things that would not work (ie on x86) - it took quite a bit of local/staging testing to get it working

currently none of the tooling is actually tested on arm - with the exception of the run that is added in this pr - so its mostly not something we hit

[MarkusTeufelberger]

I think I found the issue with your build container build:

https://github.com/envoyproxy/envoy-build-tools/blob/f3a70cf47bd91d8f6ab080e4da361cc7f8e6f24d/build_container/build_container_common.sh#L80

[phlax]

maybe - altho im wondering whether any of the subsequent code there would be necessary - gcc is already installed at this point, and links etc should have been made - defo a possibility tho

[MarkusTeufelberger]

Well you install gcc-9 from some PPA, not from official releases (likely because it is not in 18.04 - it would be in 20.04 though...). Not sure after all your packages which would be the default (no suffix) gcc in that container otherwise...

[phlax]

aargghh - this is still an issue as yarl has to be compiled on 3.10 (at least for ARM)

re general points on the image @MarkusTeufelberger - i would encourage you to raise ticket/s in the envoy-build-tools repo and/or raise it on the relevant slack channel

[phlax]

@MarkusTeufelberger I have raised a PR to update the build image with your fix here #20391

Ive also picked the update on this PR, so hopefully the arm build should be fixed now - thanks for that

[phlax]

/retest

[repokitteh-read-only]

Retrying Azure Pipelines:
Retried failed jobs in: envoy-presubmit

🐱

Caused by: a #17979 (comment) was created by @phlax.

see: more, trace.

[phlax]

cc @lizan tests are passing again

[daixiang0]

Is it real mail? I do not see it in the doc.

[phlax]

it is not - and is intended to denote that - perhaps this could be more explicit in some way

[wrowe]

Use envoy@packaging.example.com perhaps?

[phlax]

updated to envoy-ci@for.testing.only

[phlax]

@lizan would you mind giving this another pass - im v open to any suggestions on how we structure this

[adisuissa]

@lizan can you PTAL?

[alyssawilk]

@lizan this has been stalled 9 days waiting on your review. Can you please take a look today?

[phlax]

ill merge main now, and check its not failing

[lizan]

Check CI? Otherwise LGTM.
/retest

[repokitteh-read-only]

Retrying Azure Pipelines:
Retried failed jobs in: envoy-presubmit

🐱

Caused by: a #17979 (comment) was created by @lizan.

see: more, trace.

[zuercher]

Approving based on @lizan's comment now that the tests passed. @phlax I'll let you merge it when you're ready.

[phlax]

ill merge this now - i suspect this will take a few iterations to optimize, but this is a major milestone/component to adding a release pipeline