-
Notifications
You must be signed in to change notification settings - Fork 178
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
Removal of db7/kazoo-go and subsequent repo deletion breaks previous builds #154
Comments
closing this because I've fixed it with a glide mirror |
@dan-compton thanks for reporting. The changes that were in db7/kazoo-go are merged upstream, so I updated goka to use that repo instead. I probably shouldn't have deleted my fork, though. I reforked the repo in the hope that your build process passes again. Could you check that please? Or if you have another suggestion, let me know. |
@db7 We're sticking with the fork + glide mirror until we update goka as the relevant changes to tooling have already been merged internally. Thanks though. As for others, it will work fine as long as the commit sha is the same. Otherwise, it would need to be discovered and updated in their X.lock file |
Thanks for the info. I restored the db7/kazoo-go with the lastest local repo I could find. Hopefully that fixes the problem for other people. This was an unfortunate repo removal. |
This change made by contributor @db7 and the subsequent removal of github.com/db7/kazoo-go repository breaks glide/dep vendored versions of lovoo/goka due to inability to fetch db7/kazoo-go. Broken version below:
API changes likely make upgrading difficult.
The text was updated successfully, but these errors were encountered: