-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$ go get failed because of "cli" package dependency #39
Comments
May be resolved at #40. Please try it. Thanks for reporting! |
Thank you for your quick acknowledgement and operation. I've retried
Another fix, maybe on ll.17-22 of
So I want to ask a favor of you to reopen this issue. Best regards. |
Sorry for my incomplete fix. I’ll fix later. |
I fixed code at #41 and blogsync now depends latest urfave/cli (v2.1.0). However, due to this change, blogsync only works with go modules. Therefore, if you want to install blogsync with "go get", please set environment variable GO111MODULE "on" and get it with go 1.13 or later. Alternatively, you can get built binaries from GitHub Releases and use that. If you just want to use the blogsync command, it is certain in many cases. |
When I tried to install this product with command
$ go get github.com/motemen/blogsync
, or$ cd ${GOPATH}/src/github.com/motemen/blogsync && go build -o blogsync
after cloning this git repository, the following error has occurred, regardless of where the installation was tried, such as on my local machine(WindowsPowerShell) or on remote host(CircleCI-GoContainer).I guess that the dependency between
main.go
andurfave/cli
, which is mentioned as one of imported packages inmain.go
, leads this error. For your information,urfave/cli
branched off in autumn 2019, and now there are two versions of that component, thenimport
method written below may result in installation ofurfave/cli/v1
.cf. https://github.com/urfave/cli
cf. swaggo/swag#556
So I want to let you know the phenomenon, and I hope you would fix this issue.
Best regards.
The text was updated successfully, but these errors were encountered: