Please use gopkg.in for importing mgo
Menno Smits
menno.smits at canonical.com
Thu Jul 31 23:43:20 UTC 2014
Trunk is currently broken if building using a clean GOPATH because
revision 03e56dcd was recently merged which imports mgo from labix.org
instead of gopkg.in. We no longer use mgo from labix.org and godeps no
longer installs it from that location.
The following import paths should be used instead:
gopkg.in/mgo.v2
gopkg.in/mgo.v2/bson
gopkg.in/mgo.v2/txn
This was perhaps not publicised well enough but the switch was made a
couple of weeks ago.
Right now juju will only build on machines that incidentally have a
labix.org mgo install. If the machine doesn't already have it, godeps won't
install it and builds fail.
I imagine the problem revision got past the landing bot because our test
hosts still have the labix.org mgo installed. If so, this should be cleaned
up.
I will fix the problem imports in the upgrades package now.
- Menno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140801/1bd3dd56/attachment.html>
More information about the Juju-dev
mailing list