skynetservices/skynet-archive

Install fails as Doozer can't compile

Lazarus404 opened this issue · 5 comments

On executing the following (as listed in the wiki)

go get github.com/4ad/doozer
go get github.com/4ad/doozerd

Go throws an error stating

go/src/pkg/github.com/4ad/doozer/msg.pb.go:10: undefined: proto.GetString

Without Doozer, I can't run SkyNet :-(

I'm working on fixing this today, we're going to fork the doozer dependencies so that we can ensure they work with skynet.

srid commented

the official install instructions does not work for this reason.

go/src/pkg/github.com/4ad/doozer/msg.pb.go:10: undefined: proto.GetString

this particular issue was fixed in repos like github.com/ActiveState/doozerd

Hi Sridhar,

You're using the wrong version of Doozer. There's a version in the skynetservices Github account.

Lee

On 26 Jan 2013, at 18:25, Sridhar Ratnakumar notifications@github.com wrote:

the official install instructions does not work for this reason.

go/src/pkg/github.com/4ad/doozer/msg.pb.go:10: undefined: proto.GetString

this particular issue was fixed in repos like github.com/ActiveState/doozerd


Reply to this email directly or view it on GitHub.

I believe skynet should reference the correct version of doozer - it looks
like the docs are out of date. doing a "go get
github.com/skynetservices/skynet" should install everything you need.

On Sat, Jan 26, 2013 at 2:27 PM, Lee Sylvester notifications@github.comwrote:

Hi Sridhar,

You're using the wrong version of Doozer. There's a version in the
skynetservices Github account.

Lee

On 26 Jan 2013, at 18:25, Sridhar Ratnakumar notifications@github.com
wrote:

the official install instructions does not work for this reason.

go/src/pkg/github.com/4ad/doozer/msg.pb.go:10: undefined:
proto.GetString

this particular issue was fixed in repos like
github.com/ActiveState/doozerd


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHubhttps://github.com//issues/179#issuecomment-12740668.

We have forked doozer into our GitHub organization, so this should no longer be a problem.