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
Cannot go get Telegraft 0.12.1, lots of "use of internal package not allowed" #1114
Comments
that issue has long been fixed, your telegraf directory needs to be in the influxdata directory, not influxdb |
What do you mean? I just git cloned it, checked out f76739c and ran that go get command and it failed... also, cloning from influxdata instead from influxdb makes no difference for this problem. What should have been done differently? |
Then something is wrong with your Go environment, I'm sorry but I don't have time to debug go environment problems for users |
Sorry, but I wasn't asking for you to debug it but simply tell me where and what to look for as I can debug it myself :-) my point is that both on Go 1.5.3 and 1.6.1 only Telegraf shows this problem. I didn't have any issues with the same steps using other Go projects, so I assume it's Telegraf that is misbehaving. |
There's nothing wrong with Telegraf builds, I can guarantee that 100%, this might be the only project you're building with internal packages. BTW, why don't you just use |
Because code cloning, deps download (the one failing) and actual building need to be executed in separate steps in the packaging I am doing for Snappy Ubuntu Core. |
My recommendation would be that you should be cloning your repos into your GOPATH. I think if you try building a Go project with an internal directory you'll get the same results (such as https://github.com/shirou/gopsutil) |
Hi, I am trying to package Telegraf and I keep getting the errors below when calling go get. I am using Go 1.6.1 and pulling Telegraf 0.12.1 from git://github.com/influxdb/telegraf.git:
Is there any branch with the whole s/influxdata/influxdb issue fixed for a test? I read in other bug reports that this is a known problem to be addressed?
The text was updated successfully, but these errors were encountered: