Hi Juan,

On Tue, Jul 14, 2026 at 10:12 AM Juan Manuel Méndez Rey
<[email protected]> wrote:
>
> Hi,
>
> Saw Andrew's DebCamp sprint announcement -- great initiative. I tested
> three packages against dh-golang 1.66~exp2 (GO111MODULE=on) and found
> two distinct failures:
>
> 1) golang-github-brunoscheufler-aws-ecs-metadata-go (ITP #1140162)
>    FAIL: "module github.com/davecgh/go-spew/spew provides package
>    github.com/davecgh/go-spew/spew and is replaced but not required"
>    The upstream go.mod only requires testify (indirect), not its
>    transitive dep go-spew. With GO111MODULE=off this worked implicitly.
>    Likely a dh-golang issue -- it generates replace directives but not
>    the matching require for transitive deps.

I see. golang-github-davecgh-go-spew-dev doesn't provide a go.mod file.

> 2) golang-opentelemetry-collector 0.152.0 (ITP #1080354)
>    FAIL: "go.work:42: replace github.com/cncf/xds/go/udpa/data/orca/v1:
>    invalid module path"
>    The generated go.work has replace directives for cncf/xds subpaths
>    that are not valid Go module paths.

golang-github-cncf-xds-dev doesn't provide a go.mod file.

> 3) golang-opentelemetry-auto (ITP #1136684)
>    Could not test -- blocked on aws-ecs-metadata-go not being in sid yet.
>
> Separately, both auto and collector are close to the finish line. The
> remaining blockers for upload:
>
>   golang-opentelemetry-auto:
>   - Needs golang-github-brunoscheufler-aws-ecs-metadata-go uploaded (ITP 
> #1140162)
>     
> https://salsa.debian.org/go-team/packages/golang-github-brunoscheufler-aws-ecs-metadata-go
>
>   golang-opentelemetry-collector:
>   - MR pending review for update to 0.152.0+ds:
>     https://salsa.debian.org/go-team/packages/golang-opentelemetry-collector
>
> If anyone at DebCamp has a moment to review these, it would unblock
> both packages. Happy to help with the GO111MODULE=on transition --
> will keep testing and reporting.

I know what you feels. To get the pending package review is good. But
we now in the major transitions.
I hope if we have man power, we should put into in phase 1: get all
the -dev package(300 source packages)ships a go.mod file.

That will resolve a lot of error you listed here. And after that we
can check the rest of issues in phase 2.

Best regards,
-- 
-Andrew

Reply via email to