Control: tags -1 moreinfo On 08/09/26 1:06 pm, Andrew Lee (李健秋) wrote: > Package: lintian > Version: 2.140.0 > Severity: important > X-Debbugs-Cc: [email protected] > > > Dear Lintian Maintainers, > > Go Team needs help for the Module-Aware Build with new tooling `dh-go` > transition. > > Please adding a check to validate Go library (-dev) package names > against their upstream Go import paths from the root go.mod it ships. > > Background > ========== > In the Go ecosystem, the API version is specify within it's mport path > with a version suffix: eg: "github.com/foo/bar/v3" > > When the transition to new tooling `dh-go` that enables Module-Aware > Builds, we want to have a consistent naming style to prevent confusion > for both maintainers and new tooling as the new tooling is hight depends > on filesystem directory structure to maps the modules for offline > building under Go Workspace. > > The Transition Guide contains a Packaging Rules for the Package Naming > Conventions. Maintainer should appending the major API version suffix > to both source and binary package names to match with Go Import Path. > > For example: > > The first line of go.mod file contains: "module github.com/foo/bar/v3" > Package name should be: `golang-github-foo-bar-v3-dev` to match the > upstream import path in go.mod.
Lintian maintainer here. Is it not possible to have this check inside dh-go and have the package not build if this happens? You could go ahead and ask lucas/sanvila for archive rebuilds to figure out which packages need fixing. There are already 2 tags which will be no longer useful after the transition missing-xs-go-import-path-for-golang-package xs-go-import-path-differs-from-module-path I feel adding one more tag which will again go away after the transition is not a good use of my time. If it is not possible to have it via dh-go and there is another reason to add it in lintian, please let me know. Otherwise, please close this bug.
