Skip to content
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

ginkgo installation failed by Dep #513

Closed
junpayment opened this issue Jul 27, 2018 · 1 comment
Closed

ginkgo installation failed by Dep #513

junpayment opened this issue Jul 27, 2018 · 1 comment

Comments

@junpayment
Copy link

junpayment commented Jul 27, 2018

Hi contributers, thanks a great product!

Attempting to install with dep will fail.

$ dep ensure
 :
(21)  ? attempt gopkg.in/fsnotify.v1 with 1 pkgs; 0 versions to try
panic: version queue is empty, should not happen
 :

Actually I know the cause, I also know how to avoid it.

This is because the path of gopkg.in/fsnotify/fsnotify.v1 referred to by kinkgo's dependent library github.com/hpcloud/tail at v1.0.0 (latest) is different from the current one .

I make the issue about it
hpcloud/tail#146

fsnotify
https://gopkg.in/fsnotify.v1

The workaround is as follows.

Switch source ingopkg.in/fsnotify/fsnotify.v1

Write Gopkg.toml like below

[[override]]
  name = "gopkg.in/fsnotify.v1"
  source = "gopkg.in/fsnotify/fsnotify.v1"

see also golang/dep#1799 (comment)

Use the master branch of github.com/hpcloud/tail

Write Gopkg.toml like below
Because master branch of tail already solved it.

[[override]]
  branch = "master"
  name = "github.com/hpcloud/tail"

I hope to solve the root cause if possible.
Because I think that dep is still used so much and it can be predicted what vgo will be going on so I think that many users rely on dep.

@nodo
Copy link
Collaborator

nodo commented Aug 1, 2018

Hey @junpayment !

Thanks for reporting this problem and investigating the root cause! Hopefully, it will help other ginkgo users with the same problems.

I feel that this issue is not related to ginkgo directly and for now I am going to close it. Please, feel free to re-open the issue if you have questions or comments on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants