Inconsistency between go get and dep tools to how remote is resolved for git repos

[outcoldman]

What version of dep are you using (dep version)?

Build from master and latest available release (0.4.1)

What dep command did you run?

dep init

What did you expect to see? / What did you see instead?

In case of private repos when you call

go get example.com/repo.git

That makes go get to recognize that this is a git repo and clone it with default scheme git+ssh and remote will be used as example.com/repo.

See regex for the last vcs definition vcs.go#L1020, which resolves example to the repo=example.com/repo and root=example.com/repo.git and later takes repo as remote (see vcs.go#L745).

In case of dep it will use example.com/repo.git as root and as remote, which makes it impossible to make it work with go get, as you need to have a same repo to be available on remote under /repo.git and /repo paths.

[mvdan]

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!