go build一直抱怨：go.mod具有post-v0模块路径

Question

Following the release of Go 1.11, I have been trying to move my repositories to Go modules, by adding a go.mod file at their root.

One of my root libraries my.host/root is in its version 17.0.1, so I wrote in its go.mod file:

module my.host/root/v17

I tagged that version v17.0.1 as documented in the Go modules manual.

When I try to make a new Go project that uses my root library, like:

package main

import root "my.host/root/v17"

func main() {
    root.DoSomething()
}

And try to compile it, I get the following error:

go: my.host/root@v0.0.0-20180828034419-6bc78016491a: go.mod has post-v0 module path "my.host/root/v17" at revision 6bc78016491a

I am at loss figuring out why this happens. I explicitly added v17.0.1 in the go.mod file, yet every attempt at go build replaces the entry with a v0.0.0-20180828034419-6bc78016491a version which then fails because at that commit, the go.mod file module entry of my root library indeed ends with a v17, as it should.

For the record, this commit is the same as the tagged v17.0.1 version.

What am I doing wrong here? How can I debug this situation?

Answer 1

I had make two mistakes:

• My initial v17.0.0 tag would point to a commit where go.mod did not contain the v17 import path suffix. As a result, it seems Go tooling considers the whole v17 major version as a v0/v1 instead, even if later v17 tags point to a commit with a correct go.mod directive, hence the commit ID "translation".
• In my dependent projects, in the go.mod file, I mistakenly specified require my.host/root v17.0.1 instead of require my.host/root/v17 v17.0.1.

After fixing both those issues, everything seems back to normal and it works perfectly. I wish the documentation had been clearer about this but I guess this is a good opportunity to make a contribution!