This happens if you follow the instructions in the juju README.md file (under the "Getting Juju" heading):
$ go version
go version go1.6.2 linux/amd64
$ GOPATH=~/go go get -d -v github.com/juju/juju/...
...
github.com/vmware/govmomi (download)
package github.com/juju/juju/cmd/juju
imports context: unrecognized import path "context" (import path does not begin with hostname)
I believe this is due to the Juju code importing github.com/vmware/govmomi, which appears to depend on the context packaging being in the standard library, which is a Go 1.7 feature - using an older version of Go to get the Juju sources will now fail.
The options are likely to be:
- Require Go 1.7 to fetch/build Juju.
- Change the instructions to git clone juju, then use godeps to fetch the dependencies (instead of relying on `go get`).
- Import a version of govmomi that is version pinned to code prior to the switch to "context" imports.
This happens if you follow the instructions in the juju README.md file (under the "Getting Juju" heading):
$ go version com/juju/ juju/.. . com/vmware/ govmomi (download) com/juju/ juju/cmd/ juju
go version go1.6.2 linux/amd64
$ GOPATH=~/go go get -d -v github.
...
github.
package github.
imports context: unrecognized import path "context" (import path does not begin with hostname)
I believe this is due to the Juju code importing github. com/vmware/ govmomi, which appears to depend on the context packaging being in the standard library, which is a Go 1.7 feature - using an older version of Go to get the Juju sources will now fail.
The options are likely to be:
- Require Go 1.7 to fetch/build Juju.
- Change the instructions to git clone juju, then use godeps to fetch the dependencies (instead of relying on `go get`).
- Import a version of govmomi that is version pinned to code prior to the switch to "context" imports.