cmd/go: 'go list -m all' doesn't diagnose conflicts in non-imported packages #41652
Comments
The package namespace and module namespace are related, but not quite the same. The The general solution is to give the |
go list -mod mod -m all
don't return the same module list actual used when building or vendering
what |
The |
Currently vgo2nix is using
go list -mod mod -json -m all
to find out all the dependencies of current project, but we find this command will output conflicts modules.A simple example:
These too dependencies are in conflict, but not imported by code, so
go build
andgo mod vendor
runs just fine.But
go list -mod mod -m all
will list them both.Is it considered an issue of
go list
, or is there a command to serve our purpose?The text was updated successfully, but these errors were encountered: