Hi Juan, Thanks for the clarification on the chroot — that matches what I see after refreshing sid-amd64-sbuild on my packaging host. Agreed that aws-ecs-metadata-go is the remaining Build-Depends gap in sid.
salsa-ci.yml MR as requested: https://salsa.debian.org/go-team/packages/golang-opentelemetry-auto/-/merge_requests/1 Minimal change only: debian/salsa-ci.yml with the Salsa CI team recipe, and debian/gitlab-ci.yml as a thin local include wrapper (no extra SALSA_CI_DISABLE_* from my leaf policy). Happy to adjust if you want something different. On the DD upload of aws-ecs-metadata-go I will stay out of the way unless a short ping on the July debian-go thread would help. Cheers, Hermes El dom, 20 sept 2026 a las 10:38, Juan M. Méndez Rey (<[email protected]>) escribió: > > El domingo, 20 de septiembre de 2026 a las 07:09, Hermes Jesus Rodriguez > Azuaje <[email protected]> escribió: > > Hi Hermes, > > Thanks for your interest, I contributed on the majority of those packages, > and almost all Build-Depends for auto are in sid already. You might need to > update your chroot. > The only one missing is aws-ecs-metadata-go, changes are in salsa waiting for > upload. > > https://salsa.debian.org/go-team/packages/golang-github-brunoscheufler-aws-ecs-metadata-go > [1] > We made a request in July: > https://lists.debian.org/debian-go/2026/07/msg00052.html > > Regarding, splitting auto/sdk, I remember speaking with Andrew about this and > I am not wrong the outcome was to keep it together. > > Regarding salsa-ci.yml: Good catch, please, send a MR to go-team/packages/ . > > > > These are the pending items waiting for a DD: > > Upload aws-ecs-metadata-go (link above), this is the last blocker for auto. > > > PS: The go-team is involved in the Module-Aware Build Transition Plan, > resolving autopkgtest errors, and getting dh-golang 1.66 in unstable. > When things estabilizes, could be a good time to ask for sponsorships again, > unless some DD reads it and is willing to sponsor [1] > > > Cheers, > Juan >
