-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Problem with fsnotify.v1 dependency #2387
Comments
maybe we should add a dep check in ci to make sure all dependency are valid and up to date |
That is not required because the dependencies are in the vendor directory. |
Have some context on this. I believe @sbfaulkner put together a fix by making the repository name explicit wherever that package is referenced. I believe it's on the way :) |
I'll submit a PR shortly... it's a two line change (and a big vendor folder update) |
Closing. Fixed in #2392 |
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
NGINX Ingress controller version:
master
Kubernetes version (use
kubectl version
):none
Environment:
Mac OS X high sierra
What happened:
When running
dep ensure
, gettingWhen
dep ensure --update
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
As I understand this . problem was caused by renaming
gopkg.in/fsnotify.v1
package togopkg.in/fsnotify/fsnotify.v1
The text was updated successfully, but these errors were encountered: