Closed tgockel closed 6 years ago
Great idea!
Pull request welcome if you want to update it. Otherwise I'll try to do it in the next week or so.
So this is somewhat annoying...it seems that the file fetched in ensure-zookeeper-env
will be zookeeper-3.5.3-beta.tar.gz
. Despite the .tar.gz
file suffix, it is actually a non-gzipped tarball, which makes the tar -zx
fail. Changing this to tar -x
works, but of course breaks all the properly-compressed files. Aside from opening a bug against ZK's packaging, I'm not sure what to here.
Ugh, that's no fun.
Can you open a ticket on the Zookeeper Jira and link back to it here?
Generally I've found that team is reasonably responsive, especially to something like this which sounds like a very annoying packaging bug that is likely to bite a lot of folks.
Bug is ZOOKEEPER-2885. Hopefully I'll get an email when it's fixed.
Perfect, as long as you're a watcher on the JIRA ticket you'll get an email...
@tgockel now that this is fixed upstream, do you want to submit a PR containing your commit that fixes this?
It's marked as fixed, but the file hasn't propagated out to everywhere...there's some likelihood that it will not ever in a lot of mirrors, since people usually expect artifacts to be permanent.
I assume from your comment that it's breaking on Travis still... That's a bummer. I guess we'll just have to wait for 3.5.4 to drop.
Yeah...3.5.3 is beta anyway :-)
Currently,
.travis.yml
uses the to-be-releasedZOOKEEPER_VERSION=3.5.2-alpha
. The current release (as of 2017-08-24) of the 3.5 line is 3.5.3-beta. Unless there is some motivation to continue to test against the old ZK server,.travis.yml
should be updated to use the newer version.