Is it possible to put back the tar.gz sources of 3.4.7 on mirrors so that Node Zookeeper (https://github.com/yfinkelstein/node-zookeeper) client can be used without downgrading? Considering that critical bug only affects the server?
On Tue, 2 Feb 2016 at 15:05 Oleksiy Krivoshey <[email protected]> wrote: > Thanks! Waiting for 3.4.8. > > On Tue, 2 Feb 2016 at 14:56 John Sirois <[email protected]> wrote: > >> 3.4.7 had a critical bug and was pulled just after release. 3.4.8 will be >> released shortly to remedy. >> >> This has confused alot of folks. >> See, for example, this thread for more details: >> http://zookeeper.markmail.org/thread/ihvmqiow2jc47yo5 >> On Feb 2, 2016 5:19 AM, "Oleksiy Krivoshey" <[email protected]> wrote: >> >> > Hi! Can someone please explain whats happening with release on Zookeeper >> > mirrors? About a month ago 3.4.6 release (I mean tar.gz sources) >> > disappeared from all mirrors and 3.4.7 was released. Now 3.4.7 had >> > disappeared but 3.4.6 is back. This causes severe problems for widely >> used >> > client libraries such as https://github.com/yfinkelstein/node-zookeeper >> > which >> > downloads tar.gz in order to build native binding for Node.js. It was >> > updated to use 3.4.7 but of course it fails to build now because >> > >> > >> http://apache.mirrors.tds.net/zookeeper/zookeeper-3.4.7/zookeeper-3.4.7.tar.gz >> > is >> > no longer at its place. >> > >> > Is there a reason why the 3.4.7 sources disappeared from mirrors? >> > >> > Thanks! >> > >> >
