Etcd: go mod import package problem

Created on 8 Aug 2019  路  6Comments  路  Source: etcd-io/etcd

when i use go.etcd.io/etcd v3.3.13锛宱n go1.12, open go mod, build will error

ddd3b30627c94d367241a241e513ac3

this is my go.mod file
24b24deea9d7084c04a4f1cab2105aa

i use 'go mod why github.com/coreos/etcd' cmd, it show:
1418618281f8126b56a6bef4842c971
it look like go.etcd.io/etcd has some import package error in go mod, could someone help, thx

arequestion

Most helpful comment

release-3.3 uses the old org github.com/coreos please import using that org and this issue will resolve. When 3.4 is cut we will move to the new vanity path go.etcd.io/etcd

All 6 comments

release-3.3 uses the old org github.com/coreos please import using that org and this issue will resolve. When 3.4 is cut we will move to the new vanity path go.etcd.io/etcd

@hexfusion ok, i'll try to use 'github.com/coreos' package when import etcd, thank you!

@hexfusion is this now resolved?

@hexfusion is this now resolved?

It would depend on which etcd version you are trying to import.

release-3.3 and before use github.com/coreos/etcd IE v3.2.26, v3.3.15
release-3.4 on use vanity url go.etcd.io/etcd

Are you seeing a problem?

@hexfusion

Was seeing an issue with conflicts pretty hard when using 3.3 - go mod was getting confused and importing github.com/coreos github.com/etcd-io and go.etcd.io/etcd.

Now that 3.4 is out however I nuked all three of those repos, changed all my import paths to go.etcd.io and imported @3.4 - worked like a charm.

I have no issues with using 3.4 but others may find some problems with the mulitple repo names conflicting when using < 3.4

Generally, the issue comes when etcd is not explicitly set in go.mod. If you have examples of failure feel free to open a new issue so we can take a closer look.

Was this page helpful?
0 / 5 - 0 ratings