OK, I'll do necessary steps again and come up with rc1, thanks.
Rakesh
On Tue, Aug 23, 2016 at 12:20 AM, Chris Nauroth
wrote:
> Rakesh, thank you for figuring this out. Lack of running the "test"
> target would explain this.
>
> IMO, you will need to tag again, because the RC number is part of
Rakesh, thank you for figuring this out. Lack of running the "test" target
would explain this.
IMO, you will need to tag again, because the RC number is part of the tag.
Also, I don’t believe you can skip step 8 under Building. Even though code
hasn’t changed, there are still reasons that the
IIUC, you are advising me to skip the 8th step in the Building section and
just do 1, 2, 3, 4, 5, 6, 7 and 9, am I correct? Also, tagging step is not
required, 11th step.
Thanks,
Rakesh
On Mon, Aug 22, 2016 at 11:50 PM, Patrick Hunt wrote:
> You'll need to go through all the "how to release" s
You'll need to go through all the "how to release" steps again (the build
steps, not the branching, etc...) and create an "rc1" for review. Don't try
to massage the jars/tars/etc... just re-run the process to create the
.tar.gz and start a new voting thread.
Patrick
On Mon, Aug 22, 2016 at 11:14
I faced couple of issues in my local env while preparing the release and
done two time svn checkouts. Unfortunately, I had created the tarball from
my second one without invoking "test" target and just did $ant package
tar, which has created this issue.
rakesh@rakesh-Inspiron-3543:~/Rakesh/branch
Rakesh - part of running step 1 of the "building" (ant test package tar) is
that you should end up with (notice this is in the build directory):
phunt@phunt-MBP13:~/dev/zookeeper-br34[branch-3.4]$ ls
build/zookeeper-3.4.9/src/c/
ChangeLog NOTICE.txt c-doc.Doxyfile configure.ac missing
Thanks Chris, Michael for the observations and advice.
Yes, I also feel that the problem is due to missing 'install-sh' in the
tarball.
I've compared 3.4.9 tarball with previous version and found the following
files are missing in "http://people.apache.org/~rak
eshr/zookeeper-3.4.9-candidate-0/zo
I was able to make it work by running:
libtoolize --force
aclocal
autoheader
automake --force-missing --add-missing
autoconf
I’ve never had to do this for prior releases though. This is the same VM I’ve
used repeatedly for ZooKeeper release verification. It’s CentOS 7 and
autoconf 2.69.
Hi Chris,
I don't see the error you got. All C tests passed on Ubuntu, and all
configuration and compilation stage passed on OSX (on mac the linker error
is a known issue.). What I did:
* curl -O
http://people.apache.org/~rakeshr/zookeeper-3.4.9-candidate-0/zookeeper-3.4.9.tar.gz
* tar -xvzf zook
-1 (binding)
I haven't been able to run "ant clean test-core-cppunit" to build the native
code and run tests. It fails in the "create-cppunit-configure" target with the
error shown below.
My first theory was that something had gone wrong in my own build environment,
but I've confirmed that I
+1 sig/xsum are correct. RAT ran clean. I was able to start/use a number of
different size ensembles with the code. Looks good to me.
Patrick
On Thu, Aug 18, 2016 at 9:24 AM, Rakesh Radhakrishnan
wrote:
> This is a bugfix release candidate for 3.4.9. It fixes 21 issues, including
> issues that
This is a bugfix release candidate for 3.4.9. It fixes 21 issues, including
issues that affect ACL cache
in DataTree never removes entries, prevent multiple init of login object in
each ZKSaslClient instance,
ZK service becomes unavailable when leader fails to write transaction log,
upgrade netty v
12 matches
Mail list logo
