Not a bug but a request/question
when is go-ethereum moving to go modules instead of using dep?
eccles
All 4 comments
People are working on it
https://github.com/ethereum/go-ethereum/pull/19605
zjiekai
on 13 Oct 2019
Please see https://github.com/urfave/cli/issues/904 where I had issues in my own repo with go get -u.
The suggestion is to use the github.com url for urfave/cli and not the gopkg.in url.
I also had problems with go-interpreter/wagon. (also pulled in by go-ethereum.)
The caveat here is that I am currently pinned to version 1.8.27 of go-ethereum due to circumstances beyond my control so I did not report this as a bug in go-ethereum.(yet)
Hope this is helpful.
eccles
on 13 Oct 2019
Yes, this is something we want to do. Unfortunately we need to switch over our launchpad builders to snaps + make launchpad meta packages because Go 1.13 is not available on older versions of Ubuntu. Until that work is done, go modules are blocked.
karalabe
on 14 Oct 2019
I've just filed a potentially related issue.
It seems like not only does go-ethereum not use go modules, it may not be able to be used in any go module project that invokes the indirect leveldb dependency.
Pet3ris
on 31 Oct 2019
Related issues
keitaj
路
3Comments
prene
路
3Comments
wighawag
路
3Comments
JMaxU
路
3Comments
phpsamsb
路
3Comments
Most helpful comment
Yes, this is something we want to do. Unfortunately we need to switch over our launchpad builders to snaps + make launchpad meta packages because Go 1.13 is not available on older versions of Ubuntu. Until that work is done, go modules are blocked.