-
Notifications
You must be signed in to change notification settings - Fork 48
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
build failed with incorrect import? #29
Comments
🤔 hmm. I recently switched the master branch to using vgo, which is likely the cause. What steps did you take to get that error? |
|
example build log here: https://smallrepo.com/builds/20180802-041631-760e8b5c |
it's okay if you say that "go get" is no longer supported, but the import path does not look right non-the-less. or is that a vgo thingy? |
Ah... yeah, vgo isn't fully supported in mainline go yet (so If you need to use
That should auto-select version v1.1.2 (see: http://labix.org/gopkg.in for more details). |
And sorry about |
whelp. Looks like I fixed it! It seems vgo doesn't require the weird import comment any longer, which was indeed added there just for vgo. |
Closing as resolved. Work arounds shouldn't be needed. If you still run into issues, then let me know. |
I think the directory structure is changed, but not the import path hint.
The text was updated successfully, but these errors were encountered: