On Mon, Jul 7, 2014 at 8:49 PM, David Cheney <david.che...@canonical.com> wrote: > I don't want to introduce another thing to break CI, we already pull > from github which is bad enough, but going via gopkg.in introduces an > additional point of failure which can further reduce the already > bullet ridden credibility of our CI.
Again, gopkg.in sits in a reliable deployment, with a provable track record. > I also don't want to start introducing versioned import paths into > Juju without serious discussion of how to prevent two different > versions of a package transitively. go list -f '{{range .Deps}}{{printf "%s\n" .}}{{end}}' | grep gopkg.in | sort -u | sed 's/\.v[0-9]\+$/\.vN/' | uniq -c | sed '/ 1 /d' > I am NOT LGTM on any change that introduces gopkg.in redirected import > paths until the issue above is resolved. Okay, that's done. gustavo @ http://niemeyer.net -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev