badger: Go build broken, missing tag v2.0.0-rc.2
What version of Go are you using (go version)?
$ go version go version go1.12.5 linux/amd64
What version of Badger are you using?
v2.0.0-rc.2
Does this issue reproduce with the latest master?
yes
What are the hardware specifications of the machine (RAM, OS, Disk)?
AWS EC2, x86_64 GNU/Linux
What did you do?
Install ipfs cluster,
git clone https://github.com/ipfs/ipfs-cluster.git export GO111MODULE=on # optional, if checking out the repository in $GOPATH. go install ./cmd/ipfs-cluster-service
What did you expect to see?
go install command complete. I did same installation 3 hours ago with no this dependency error.
What did you see instead?
go: github.com/dgraph-io/badger@v2.0.0-rc.2+incompatible: unknown revision v2.0.0-rc.2
Would it be a tag issue in recent a few hours? Thank you!
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (3 by maintainers)
Commits related to this issue
- chore(ci): Fix dgraph-io badger issue. See https://github.com/dgraph-io/badger/issues/886#issuecomment-505500955 for more context. — committed to qri-io/qri by dustmop 5 years ago
- Hack to get around badgerdb tag fiasco https://github.com/dgraph-io/badger/issues/886 — committed to quorumcontrol/jasons-game by deleted user 5 years ago
- Use GOPROXY As suggested in https://github.com/dgraph-io/badger/issues/886#issuecomment-505500955 — committed to come-maiz/ipfs-snap by come-maiz 5 years ago
- Bump badger to 2.0.0.rc2 Broken currently here: go: finding github.com/zippoxer/bow latest go: github.com/dgraph-io/badger@v2.0.0-rc.2+incompatible: go.mod has post-v2 module path "github.co... — committed to rubiojr/bow by rubiojr 5 years ago
- Bump badger to 2.0.0.rc2 Broken currently here: go: finding github.com/zippoxer/bow latest go: github.com/dgraph-io/badger@v2.0.0-rc.2+incompatible: go.mod has post-v2 module path "github.co... — committed to rubiojr/bow by rubiojr 5 years ago
Try running
go clean -modcacheand then for applications that depend on the tag that was messed up setexport GOPROXY='https://proxy.golang.org'before building.proxy.golang.org which will be default in 1.13, contains original source code for the tag that was removed and then re-added. Unfortunately, when the tag was readded it was updated to latest/master which is not compatible with the code that was there before.