Hi Nilesh, On Wed, Jul 15, 2026 at 12:28 AM Nilesh Patra <[email protected]> wrote: > Please file bugs against lintian otherwise these will definitely slip > my/others > radar. I am not clear on rest of the items for lintian on that wiki so a > proper > bug report along with proposed tag and explanation will help.
Thanks for the feedback. Before we file a formal lintian bug report. This seems like a great opportunity to address a policy update within Debian Go Team. As we are transitioning to modern, module-aware builds, we should align our Debian package naming policy directly with Go import path logic. This will help dh-golang resolve dependencies automatically and also make package name much easier for humans to identify. For example, take the import path: [github.com/spiffe/go-spiffe] Looking at its official go package status on upstream: https://pkg.go.dev/github.com/spiffe/go-spiffe This import path defaults to v1. However, v2 is available under a different import path: https://pkg.go.dev/github.com/spiffe/go-spiffe/v2 Currently in our archive, we packaged the v2 release without the "-v2" suffix in the package name: golang-github-spiffe-go-spiffe | 2.5.0-1 | stable | source golang-github-spiffe-go-spiffe | 2.6.0-1 | testing | source golang-github-spiffe-go-spiffe | 2.6.0-2 | unstable | source Because the import paths [github.com/spiffe/go-spiffe] and [github.com/spiffe/go-spiffe/v2] are treated as entirely different packages by Go upstream. Not naming them the same way in Debian confuses dh-golang's automatic mapping and forces maintainers to manually inspect the packaging versions to figure out which major version is actually inside the package. Matching our Debian package names to the upstream Go import path logic (e.g., using a -v2 suffix for v2 modules) will eliminate the confusion, and makes the module-aware builds much easier and smoother for packaging in the future. > I've meanwhile implemented a check for import path value mismatching go.mod > and > opened a MR > > https://salsa.debian.org/lintian/lintian/-/merge_requests/757 Thank you very much. I have updated this into the wiki page for this sprint. Happy hacking, -- -Andrew
