-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
go get fails on Go < 1.6 #2124
Comments
Please use http://discuss.gohugo.io/ for questions (this may feel like an bug, but is more related to your Go setup). |
I'll reopen this, as this is also happen on our build server: https://travis-ci.org/spf13/hugo/jobs/128242105 But only on Go 1.5.4. Mystery, hopefully only temporary. |
Glad it got reopened, pretty sure my Go setup is correct so was
disappointed to have it just closed without at least a request for more
clarification. :)
FWIW, I'm on 1.5.4 as well, as that's the latest I get with Fedora 23. I
downloaded a prebuilt release so this isn't a blocker, but thought you'd
appreciate the heads-up that `go get` wasn't working for some of us.
Thanks.
|
Sure, I will investigate further if this continues. |
Seems we're not alone; he/she deleted the master branch; looks like Go 1.6 handles it fine, Go 1.5 not so much. Looks like we should look into vendoring sooner rather than later ... |
go get
installation instructions don't work
In looking into this, I encounter the problem with 1.6.2. On a test machine I updated Go to 1.6.2 and did a
In looking at $GOPATH/src/github.com/kr/text the only branch it has is master, so I'm not sure what is going on at this point. |
What you are looking at is unrelated (you have repo out of synch -- aka someone did a push -f ... annoying but happens). The issue described here doesn't happen in Go 1.6.*. |
Oops, I pasted the wrong output. Also when I redid it on a new VM it worked as expected...sorry about the noise. |
This issue does raise the question of what Hugo's policy for support of non-current versions of Go is, or should be. Sorry it that's been stated elsewhere and I missed it. The installation instructions for Go always point people to the latest release of Go. In my experience, it is a common expectation that developers will be on the current release of Go, unless they have specific needs or reasons not to be. One example would be JuJu and sticking with 1.4 (the last I checked) because of the longer compile times introduced by switching to the pure Go compiler. I realize that there are people that prefer using their distro's package manager to install Go but that often results in an old version of Go and the Go installation instructions does not suggest using package managers: https://golang.org/doc/install. In my experience Go installed by package managers are usually outdated and may be missing executables that are normally part of Go, e.g. . As an example, I installed Go, using the package manager on a couple of Ubuntu LTS boxes. Doing a While Go does have a backwards compatibility guarantee, there are exceptions and it does not cover everything. This is a situation where the library in question modified their repo to take advantage of new functionality. |
No, this issue raises the question about vendoring of third-party libs. We're gonna do that, eventually. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Just cut-and-pasted the
go get
command from the README. It seems to download the packages successfully, but I don't have ahugo
command in my GOPATH.Thanks.
The text was updated successfully, but these errors were encountered: