cmd/go: one new module error is backwards, another seemed backwards

[thepudds]

What version of Go are you using (go version)?

go1.13rc1

Does this issue reproduce with the latest release?

Not with Go 1.12, but yes with Go 1.13 rc1.

Issue 1

I think this new Go 1.13 error message is incorrectly swapping the two module paths in the final two lines of the error message:

        github.com/Sirupsen/logrus: github.com/Sirupsen/[email protected]: parsing go.mod:
        module declares its path as: github.com/Sirupsen/logrus
                but was required as: github.com/sirupsen/logrus

Given the v1.4.2 version of that module declares its path as github.com/sirupsen/logrus, I think the correct form of the error would be:

        github.com/Sirupsen/logrus: github.com/Sirupsen/[email protected]: parsing go.mod:
        module declares its path as: github.com/sirupsen/logrus
                but was required as: github.com/Sirupsen/logrus

Example from scratch:

$ cd $(mktemp -d)
$ go1.13rc1  mod init tempmod
$ cat <<EOF > main.go
package tempmod
import _ "github.com/docker/libcompose/docker"
EOF

$ go1.13rc1 build
[...]
go: tempmod imports
        github.com/docker/libcompose/docker imports
        github.com/Sirupsen/logrus: github.com/Sirupsen/[email protected]: parsing go.mod:
        module declares its path as: github.com/Sirupsen/logrus
                but was required as: github.com/sirupsen/logrus

Issue 2

When I first saw this next error message in the wild, at first I thought it was backwards, but later concluded it was just potentially ambiguous (I think?):

$ go1.13rc1 get github.com/iiinsomnia/[email protected]
go: finding github.com v3.0.0
go: finding github.com/iiinsomnia v3.0.0
go: finding github.com/iiinsomnia/yiigo v3.0.0
go: finding github.com/iiinsomnia/yiigo v3.0.0
go get github.com/iiinsomnia/[email protected]: github.com/iiinsomnia/[email protected]: 
 invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v3

In particular, it is not immediately clear which major version should be v0 or v1, not v3 -- the major version after the @, or the major version in the module path on the module line in the go.mod. Because it leads off with module contains a go.mod file immediately before talking about the problematic major version, it seems like it is suggesting the major version in the go.mod file should be v0 or v1 (which is not the correct resolution, and you can't even have a v0 or v1 in the module line for a go.mod unless it is a corner case like gopkg.in).

In this example, there is a go.mod at v3.0.0, but that go.mod is missing the required /v3 at the end of the module path on the module line. As it stands, I think the error message is trying to say it would be acceptable to have a @v0.x.x or @v1.x.x in the go get for that go.mod? But that was not the way it read at first read, and moreover, one could at least argue that is not the fundamental error, which is really that the major version after the @ does not agree with the (missing) major version in the module path on the module line (and depending on how you look at it, that the go get is also missing the /v3 before the @).

I have seen other people read this second error message backwards as well. (Side note: I'm not sure why it emits go: finding github.com/iiinsomnia/yiigo v3.0.0 twice).

Finally, sorry -- this probably should have been two separate issues.

CC @jayconrod @bcmills

[bcmills]

🤦‍♂️

[bcmills]

I think I can justify cherry-picking the fix for the swapped error message into the 1.13 release, but I'm not so sure about the compatibility error.

(That should be […] text comes from module.MatchPathMajor.)

[gopherbot]

Change https://golang.org/cl/191997 mentions this issue: cmd/go/internal/modload: fix swapped paths in error message

[bcmills]

@gopherbot, please backport to 1.13: we should at least fix the reversed error message.

[gopherbot]

Backport issue(s) opened: #33885 (for 1.13).

Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases.

[gopherbot]

Change https://golang.org/cl/191972 mentions this issue: [release-branch.go1.13] cmd/go/internal/modload: fix swapped paths in error message

[abraithwaite]

I might not be the best to comment on this, but as it stands now, this error message is pretty hard to understand. It's unclear which action I should take as either a module maintainer or a module consumer what to do. In this case, I am both and still unsure what to do.

In our case, we're attempting to convert modules which already have been tagged past v2.* into the proper form: adding the suffix to the module name in go.mod and re-releasing it.

For reference, as far as we can tell, we've added everything needed here:

segmentio/stats@6ed1dc3

However, trying to get it from a brand new module (and a clean mod cache):

16:01:10 $ GO111MODULE=on GOPROXY=direct go get github.com/segmentio/stats/[email protected]
go: extracting github.com/segmentio/stats/v4 v4.5.0
go: finding github.com/segmentio/stats v4.5.0
go get github.com/segmentio/stats/[email protected]: github.com/segmentio/[email protected]: invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v4

Maybe related: #34383

[abraithwaite]

For my own sanity, I checked to see if this issue could be reproduced for modules which have a "correct" git history. that is: the go.mod package directive has been updated to include the vX suffix throughout this history, for tags that reference a major version. It does still trigger the bug.

This repo has the correct v2 suffix in the go.mod file for the v2.0.0 and v2.1.0 tags and it still triggers this issue.

[imissyouso]

hi. I have similar issue with my repository https://github.com/imissyouso/textmagic-rest-go/tree/v2.0.343

$ go get github.com/imissyouso/[email protected]: github.com/imissyouso/[email protected]: invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v2

[abraithwaite]

hi. I have similar issue with my repository https://github.com/imissyouso/textmagic-rest-go/tree/v2.0.343

For this one, you might be missing the trailing v2 suffix in the get command:

github.com/imissyouso/[email protected]
should be
github.com/imissyouso/textmagic-rest-go/[email protected]

(but I still think this is a usability problem nonetheless)

[crazybber]

issue still in go1.13.3.
try cmd in https://github.com/Microsoft/vscode-go/wiki/Go-tools-that-the-Go-extension-depends-on

go get -u -v github.com/ramya-rao-a/go-outline
.......
go get -u -v golang.org/x/lint/golint
.....

gometalinter --install

work fine in win cmd .
in bash/powershell/pwsh.

it will reproduce the above issue1 .

go: finding github.com/golang/lint latest
go: github.com/golang/lint/golint: github.com/golang/[email protected]: parsing go.mod:  
        module declares its path as: golang.org/x/lint
                but was required as: github.com/golang/lint
WARNING: failed to install one or more linters: exit status 1 (installing individually)
go: finding github.com/golang/lint latest
go: github.com/golang/lint/golint: github.com/golang/[email protected]: parsing go.mod:  
        module declares its path as: golang.org/x/lint
                but was required as: github.com/golang/lint
WARNING: failed to install github.com/golang/lint/golint: exit status 1

same time, one more issue:

go get -v -u github.com/uudashr/gopkgs/cmd/gopkgs       

work fine in win cmd .
in Bash/powershell/pwsh.
it will produce :

go: finding github.com/uudashr/gopkgs/cmd/gopkgs latest
go: finding github.com/uudashr/gopkgs/cmd latest
go get: github.com/uudashr/gopkgs/cmd/[email protected] requires
        github.com/uudashr/gopkgs/[email protected]: reading github.com/uudashr/gopkgs/go.mod at revision v2.0.3: unknown revision v2.0.3

ref : https://github.com/uudashr/gopkgs

[bcmills]

@crazybber, both of those error messages are correct as far as I can tell. The module declares its path error correctly shows golang.org/x/lint per its go.mod file, and there really is no v2.0.3 tag in github.com/uudashr/gopkgs at the moment.

[bcmills]

I'm going to close this issue to reduce confusion. @thepudds, feel free to file a separate issue for the second error message.