Hi Juan (and go-team), I am packaging helm.sh/helm/v4 and related leafs toward kzero (ITP #1142432). The estimate pulls in go.opentelemetry.io/auto/sdk via github.com/distribution/distribution/v3.
Your ITP #1136684 (golang-opentelemetry-auto) covers that import path (and the wider auto / eBPF tree). It is not in the archive yet; I am not filing a competing ITP. Local rebuild of go-team/packages/golang-opentelemetry-auto on 2026-09-20 failed on Build-Depends: several packages have no candidate in sid (e.g. aws-ecs-metadata-go, opentelemetry-operations-go, sqlparser, opentelemetry-collector) and others are too old vs debian/control (ebpf, multierr, x-arch, otel, contrib, …). Two questions: 1) What is the current status / next step for landing this in unstable? 2) Would you be open to packaging go.opentelemetry.io/auto/sdk as a smaller leaf first (closer to the original auto-sdk ITP text — runtime deps mostly already in Debian), with the full eBPF auto package following later? If you prefer to keep one source package, I can instead help with missing leaf Build-Depends one at a time under go-team, if that is useful. Separately: I run a small HTTPS staging apt on https://packaging.hermesrodriguez.com/apt (personal MVP — not Debian). If it helps your local rebuilds or Salsa CI EXTRA_REPOSITORY while leaf -dev packages wait for unstable, I can publish built .debs there and share a one-line sources.list / EXTRA_REPOSITORY snippet. Say the word and which packages you want mirrored. One more small note on both Salsa trees (go-team/packages and your mendezr fork, debian/sid): there is debian/gitlab-ci.yml only — no debian/salsa-ci.yml. It still includes the old pkg-go-tools pipeline/test-archive.yml, and the project ci_config_path is unset (null). Current go-team / Flight Deck preference is debian/salsa-ci.yml (Salsa CI team recipe). Happy to send a tiny MR that adds salsa-ci.yml and turns gitlab-ci.yml into a thin local include wrapper, if you want — same pattern as recent leafs. Happy to coordinate on Salsa or on this bug. Thanks for the work so far. Best regards, Hermes Rodríguez
