Re: [go-nuts] Re: If v2.x.y+incompatible exists, then getting the modules based v3 version will always fail?

2019-09-14 Thread T L
On Friday, September 13, 2019 at 3:19:55 PM UTC-4, andrey mirtchovski wrote: > > are you following the steps outlined below? > > https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher > > in particular, for a v2 (or v3) it states that the go.mod file must be > updated: > >

Re: [go-nuts] Re: If v2.x.y+incompatible exists, then getting the modules based v3 version will always fail?

2019-09-13 Thread andrey mirtchovski
are you following the steps outlined below? https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher in particular, for a v2 (or v3) it states that the go.mod file must be updated: > Update the go.mod file to include a /v3 at the end of the module path in the > module directive

[go-nuts] Re: If v2.x.y+incompatible exists, then getting the modules based v3 version will always fail?

2019-09-13 Thread T L
I really don't get how modules are got. I create another repo with all versions are module based, but it still fails on getting v2. $ go get github.com/go101/mod_versions_b/v2@latest go: finding github.com/go101/mod_versions_b/v2 v2.1.1 go get github.com/go101/mod_versions_b/v2@latest: module