You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that MinterTeam/minter-go-node directly depends on github.com/tendermint/[email protected]. But module github.com/tendermint/tm-db at version v0.6.6 uses replace directive to replace dependency github.com/tecbot/gorocksdb with github.com/roysc/gorocksdb.
According to Go Modules wikis, replace directives in modules other than the main module are ignored when building the main module.
It means such replace usage in dependency's go.mod cannot be inherited when building main module. And it turns out that MinterTeam/minter-go-node indirectly relies on github.com/tecbot/gorocksdb, which is different from the replaced dependency tendermint/tm-db needed.
To avoid such inconsistency, the best approach is bumping the version of github.com/tendermint/tm-db since the latest release(v0.6.7) of github.com/tendermint/tm-db has eliminated the replace usage in go.mod.
The text was updated successfully, but these errors were encountered:
It seems that
MinterTeam/minter-go-node
directly depends ongithub.com/tendermint/[email protected]
. But modulegithub.com/tendermint/tm-db
at versionv0.6.6
uses replace directive to replace dependencygithub.com/tecbot/gorocksdb
withgithub.com/roysc/gorocksdb
.According to Go Modules wikis,
replace
directives in modules other than themain module
are ignored when building the main module.It means such replace usage in dependency's go.mod cannot be inherited when building main module. And it turns out that
MinterTeam/minter-go-node
indirectly relies ongithub.com/tecbot/gorocksdb
, which is different from the replaced dependencytendermint/tm-db
needed.To avoid such inconsistency, the best approach is bumping the version of
github.com/tendermint/tm-db
since the latest release(v0.6.7) ofgithub.com/tendermint/tm-db
has eliminated the replace usage in go.mod.The text was updated successfully, but these errors were encountered: