Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/go: "conflicts with" message is too vague when one path is a package and the other is a module #46426

bcmills opened this issue May 27, 2021 · 0 comments


Copy link

@bcmills bcmills commented May 27, 2021

From a Slack conversation with @myitcv and @jayconrod:

$ go get -d
go get: conflicts with (v1.0.0)

-- go.mod --
go 1.17
replace ( v1.0.0 => ./mod v2.0.0 => ./modv2
-- mod/go.mod --
go 1.17
-- mod/v2/v2.go --
package v2
-- modv2/go.mod --
go 1.17

That error message is decidedly suboptimal: it's saying that the constraint (which is interpreted as a module path) conflicts with (which is a package query resolving to the same module at v1.0.0).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant