ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services.
Created attachment 229917 [details] apache-zookeeper-3.3.0.ebuild This ebuild just copies the java to a good location. It does not compile from source.
In my overlay... http://git.wolf31o2.org/gitweb/?p=overlays/wolf31o2.git;a=commit;h=a95e707027db5227a92fe6b82c22e835b9958632
Hi guys, I have packaged (again) sys-cluster/zookeeper-3.4.5 with added features and a proper init script (inspired by the almost too many ebuilds of this package) This package includes the C client and python client bindings. If you find the time to give it a go, please bump this bug. I'd be willing to move it to official portage and maintain it if I get some users feedbacks. Cheers
(In reply to Ultrabug from comment #3) > I have packaged (again) sys-cluster/zookeeper-3.4.5 with added features and > a proper init script (inspired by the almost too many ebuilds of this > package) In my overlay ofc sorry : ultrabug on layman
zookeeper fails: python2_7: running distutils-r1_run_phase distutils-r1_python_install_all /var/tmp/portage/sys-cluster/zookeeper-3.4.6/work/zookeeper-3.4.6/contrib/zkpython rm: cannot remove ‘bin/*.cmd’: No such file or directory * ERROR: sys-cluster/zookeeper-3.4.6::ultrabug failed (install phase): * (no error message) * * Call stack: * ebuild.sh, line 93: Called src_install * environment, line 6409: Called die * The specific snippet of code: * rm bin/*.cmd || die;
Created attachment 400486 [details] install fails
The following VMs are available for generation-2: 1) IcedTea JDK 7.2.5.3 [icedtea-7] *) IcedTea JDK 6.1.13.5 [icedtea-bin-6] #COMPILERS="ecj-3.1 jikes javac" CLASSPATH just lists a variety of choices. Which would be the best to use to install zookeeper? Other suggestions?
duplicated zookeeper-3.4.6 to /usr/local/portage/sys-cluster/zookeeper/ Fri Apr 3 2015 zookeeper-3.4.6-r1.ebuild log4j is a software that is needed so 'dev/java-log4j needs to be added as a compile dependency. ran 'ebuild zookeeper-3.4.6-r1.ebuild manifest edited the -r1 version to remove this troubling line: rm bin/*.cmd || die as it fails with ultrabug's zookeeper version. There is this interesting dir now: /var/tmp/portage/sys-cluster/zookeeper-3.4.6-r1/work/zookeeper-3.4.6/bin with these files: README.txt zkCli.cmd zkEnv.cmd zkServer.cmd zkCleanup.sh zkCli.sh zkEnv.sh zkServer.sh cat README.txt This directory contain scripts that allow easy access (classpath in particular) to the ZooKeeper server and command line client. Files ending in .sh are unix and cygwin compatible Files ending in .cmd are msdos/windows compatible Next I get this error: python2_7: running distutils-r1_run_phase distutils-r1_python_install_all /var/tmp/portage/sys-cluster/zookeeper-3.4.6-r1/work/zookeeper-3.4.6/contrib/zkpython /var/tmp/portage/sys-cluster/zookeeper-3.4.6-r1/temp/environment: line 6402: conf/zoo.cfg: No such file or directory * ERROR: sys-cluster/zookeeper-3.4.6-r1::jackslap failed (install phase): * sed failed * * Call stack: * ebuild.sh, line 93: Called src_install * environment, line 6402: Called die * The specific snippet of code: * sed "s:^dataDir=.*:dataDir=${DATA_DIR}:" conf/zoo_sample.cfg > conf/zoo.cfg || die "sed failed"; This missing file is in this dir: /var/tmp/portage/sys-cluster/zookeeper-3.4.6/work/zookeeper-3.4.6/conf/zoo_sample.cfg So the DIR paths are confused in the ebuild?
I clean up my system, including java and others and now the ultrabug repo :: sys-cluster/zookeeper-3.4.6 installs just fine. I'm not sure how to test zookeeper. I have a mesos-0.22 ebuild that installs and seems to work (bgo 510912) and there is an apache-spark ebuild (bgo 523412) that just might work now too, since spark-1.5.0 has been released. I stuggle a bit with maven et. al...... Testing the (3) mesos + zookeeper + spark, together is my ultimate goal. hth, James
(In reply to James Horton from comment #9) > I clean up my system, including java and others and now > the ultrabug repo :: sys-cluster/zookeeper-3.4.6 installs > just fine. I'm not sure how to test zookeeper. I have > a mesos-0.22 ebuild that installs and seems to work (bgo 510912) > and there is an apache-spark ebuild (bgo 523412) > that just might work now too, since spark-1.5.0 has been released. > I stuggle a bit with maven et. al...... > > Testing the (3) mesos + zookeeper + spark, together is my ultimate goal. > > hth, > James As discussed with you James, we'll work on integrating all this in my overlay to get a potent test from willing users. Maybe we'll get confident enough to get it into the tree afterwards ;)
Gone on tree since then, closing