On Wed, Sep 9, 2026 at 9:11 PM Dr. Tobias Quathamer <[email protected]> wrote: > In general, I would welcome the check that Andrew has suggested.
I filed this bug report because I have seem some maintainers fixed the Go import path mismatch issue in the transition, but they did not rename their packages, even though I wrote documentation about it. They still keep their Go Application build-depends on the legacy -dev packages. This makes the transition done half way and they need to do the transition work again later. I think we do need somehow to hint the maintainers ASAP to also rename the package to match the Go import path so we do not have to check anad tell them to fix their package twice. The `dh-go` still not completely impletemented for all cases to build module-aware builds yet(I have found a issue to build google-cloud packages). I'm afraid adding the checks to fail the builds in `dh-go` will probably complex the impletemention for fully module-aware builds in dh-go. > However, if this is a lot of work for you, then by all means, please do > *not* implement this. I think we can live without that check as well. I already can imagine what a mess will be if we have to live without the check in this transition. Best regards, -- -Andrew
