search

mesosphere-backup / etcd-mesos

self-healing etcd on mesos!
Apache License 2.0
67 stars 19 forks source link

missing latest mesos-go in Godeps? #80

Closed jdef closed 9 years ago

jdef commented 9 years ago 
$ make
rm bin/etcd-*
rm -f /home/vagrant/etcd-mesos-workspace/src/github.com/mesosphere/etcd-mesos/Godeps/_workspace/src/""github.com/mesosphere"/etcd-mesos"
mkdir -p /home/vagrant/etcd-mesos-workspace/src/github.com/mesosphere/etcd-mesos/Godeps/_workspace/src/"github.com/mesosphere"
ln -s /home/vagrant/etcd-mesos-workspace/src/github.com/mesosphere/etcd-mesos /home/vagrant/etcd-mesos-workspace/src/github.com/mesosphere/etcd-mesos/Godeps/_workspace/src/""github.com/mesosphere"/etcd-mesos"
go build -o bin/etcd-mesos-executor cmd/etcd-mesos-executor/app.go
go build -o bin/etcd-mesos-scheduler cmd/etcd-mesos-scheduler/app.go
# github.com/mesosphere/etcd-mesos/scheduler
Godeps/_workspace/src/github.com/mesosphere/etcd-mesos/scheduler/scheduler.go:964: unknown mesosproto.TaskInfo field 'Discovery' in struct literal
make: *** [bin/etcd-mesos-scheduler] Error 2
spacejam commented 9 years ago

This is due to awkwardness of having to maintain different versions of mesos-go for different mesos targets. Master is in a weird state where it has mesos-go bindings compatible with 0.22 but features that were added for a later version. I've been pushing non-mesos-go changes to master, and keeping version specific stuff into their own branches. But I think I should probably push the latest mesos-go into master and then revert it on the 22 branch.

spacejam commented 9 years ago

https://github.com/mesosphere/etcd-mesos/pull/82