Re: FreeBSD Port: consul-0.7.1

2016-11-14 Thread Steve Wills
Ah, I see. Seems like version/version_base.go isn't overriding version/version.go properly, so I have to patch it. I'm not sure why that's happening right now. Should be fixed now. Steve On 11/13/2016 17:43, Douglas Thrift via freebsd-ports wrote: > Hmm, > > I upgraded to 0.7.1_1 and "consul -v

Re: FreeBSD Port: consul-0.7.1

2016-11-13 Thread Douglas Thrift via freebsd-ports
Hmm, I upgraded to 0.7.1_1 and "consul -v" is correctly showing v0.7.1, but now the "Build" column in the output of "consul members" is just blank. Douglas William Thrift On 11/12/2016 3:41 PM, Steve Wills wrote: > Fixed, thanks for the heads up. > > Steve > > On 11

Re: FreeBSD Port: consul-0.7.1

2016-11-12 Thread Steve Wills
Fixed, thanks for the heads up. Steve On 11/12/2016 12:29, Douglas Thrift wrote: > Hello, > > It looks like the new update to consul 0.7.1 is reporting its version as > "unknown-unknown" rather than "0.7.1". I'm guessing something changed in > the upstream build process. > > This shows up when

FreeBSD Port: consul-0.7.1

2016-11-12 Thread Douglas Thrift via freebsd-ports
Hello, It looks like the new update to consul 0.7.1 is reporting its version as "unknown-unknown" rather than "0.7.1". I'm guessing something changed in the upstream build process. This shows up when running "consul -v" and in the "Build" column when running "consul members". I'm guessing someth