Hey there, regarding the docker images: klaemo/couchdb:2.0-rc2 is currently building on docker hub. it starts a single node.
klaemo/couchdb:2.0-dev will also follow the release candidates, but it will start the preconfigured dev cluster. Feel free to give them a spin (build could still take a few minutes though) Clemens > Am 20.07.2016 um 14:06 schrieb Clemens Stolle <[email protected]>: > > docker image for 2.0.0-RC1 will be up soon :) > > Am Fr, 15. Jul 2016, um 18:53, schrieb Jan Lehnardt: >> We’ve tagged RC1, build here as usual: >> >> http://couchdb.apache.org/release-candidate/2.0/ >> >> @Clemens, the git tag is `2.0.0-RC1` :) >> >> Best >> Jan >> -- >> >> >> >> >>> On 15 Jul 2016, at 08:53, Jan Lehnardt <[email protected]> wrote: >>> >>> In fact, now all commits to couchdb.git master will produce a tarball here, >>> automatically: http://couchdb.apache.org/release-candidate/2.0/ — Latest >>> should be on top, but make sure to check the date (requires JS). >>> >>> This custom Jenkins build produces it: >>> http://ci.couchdb.org:8888/job/CouchDB-Dist/ >>> >>> >>> Best >>> Jan >>> -- >>> >>> >>>> On 14 Jul 2016, at 22:55, Jan Lehnardt <[email protected]> wrote: >>>> >>>> New tarball with the changes here: >>>> >>>> https://home.apache.org/~jan/couchdb/2.0/RC/apache-couchdb-2.0.0-2dddaf0.tar.gz >>>> >>>> Best >>>> Jan >>>> -- >>>> >>>>> On 14 Jul 2016, at 19:04, Robert Newson <[email protected]> wrote: >>>>> >>>>> This is now fixed on master. >>>>> >>>>> Sent from my iPhone >>>>> >>>>>> On 14 Jul 2016, at 14:19, Jan Lehnardt <[email protected]> wrote: >>>>>> >>>>>> Confirmed trying to run with R19 on Ubuntu, make succeeds, but dev/run >>>>>> -n 1 fails with this in dev/logs/node1.log: >>>>>> >>>>>> {"init terminating in >>>>>> do_boot",{{error,{{shutdown,{failed_to_start_child,"couch_epi|chttpd_auth|keeper",{{badmatch,{{error,undef},{state,couch_epi_functions_gen,undefined,chttpd_auth,couch_epi_functions,couch_epi_functions_gen_chttpd_auth,undefined,providers,{undefined,undefined}}}},[{couch_epi_module_keeper,do_reload_if_updated,1,[{file,"src/couch_epi_module_keeper.erl"},{line,120}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,328}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,247}]}]}}},{couch_epi_app,start,[normal,[]]}}},[{boot_node,start_app,3,[{file,"dev/boot_node.erl"},{line,134}]},{lists,foldl,3,[{file,"lists.erl"},{line,1263}]},{boot_node,start_app,3,[{file,"dev/boot_node.erl"},{line,124}]},{lists,foldl,3,[{file,"lists.erl"},{line,1263}]},{init,start_em,1,[]},{init,do_boot,3,[]}]}} >>>>>> >>>>>> >>>>>> Best >>>>>> Jan >>>>>> -- >>>>>> >>>>>>> On 14 Jul 2016, at 12:14, Johannes Jörg Schmidt <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>> I'm so exited about the release candidate I can't tell \o/ Thank you so >>>>>>> much! >>>>>>> >>>>>>> I tried to install the RC on my Arch Linux system. Sadly on my machine >>>>>>> is Erlang version 19 installed [1] but CouchDB requires Erlang up to >>>>>>> version 18 but not 19 and therefore did not build. >>>>>>> >>>>>>> I thought I give it a shot and changed rebar.config.script and >>>>>>> src/snappy/rebar.config to allow Erlang 19. The build went fine than but >>>>>>> CouchDB didn't start: >>>>>>> >>>>>>> [ * ] Check node at http://127.0.0.1:15984/ ... failed: <urlopen error >>>>>>> [Errno 111] Connection refused> >>>>>>> >>>>>>> I'm aware that this maybe was a silly try but why not :) - But what >>>>>>> would it take to support Erlang 19? >>>>>>> >>>>>>> Johannes >>>>>>> >>>>>>> [1]: https://www.archlinux.org/packages/community/x86_64/erlang-nox/ >>>>>>> >>>>>>>> On 13.07.2016 18:35, Jan Lehnardt wrote: >>>>>>>> Dear dev@, >>>>>>>> >>>>>>>> it’s been about three years in the making, but I think we are now at a >>>>>>>> point where we can start the CouchDB 2.0 release candidate phase. >>>>>>>> >>>>>>>> Before we set the process in stone, please give the tarball linked >>>>>>>> below a try, as if were the CouchDB 2.0 release, and please report any >>>>>>>> issues back. >>>>>>>> >>>>>>>> The instructions in >>>>>>>> https://docs.google.com/document/d/1BtndYr-0KDQTqBSLVdJoR_8C5ObYjT1RBo_Qyh5ykdQ/edit#heading=h.hxt36ze66vb3 >>>>>>>> (ignore the Docker bits above) should get you going with either a >>>>>>>> single-machine test cluster, or a proper multi-node setup. >>>>>>>> >>>>>>>> If any of this doesn’t work or is confusing, please report back here >>>>>>>> or in JIRA. >>>>>>>> >>>>>>>> Without further ado: >>>>>>>> >>>>>>>> https://home.apache.org/~jan/couchdb/2.0/RC/apache-couchdb-2.0.0-92c95de.tar.gz >>>>>>>> >>>>>>>> Happy testing and thanks in advance for your feedback! >>>>>>>> >>>>>>>> Best >>>>>>>> Jan >>>>>> >>>>>> -- >>>>>> Professional Support for Apache CouchDB: >>>>>> https://neighbourhood.ie/couchdb-support/ >>>>>> >>>>> >>>> >>>> -- >>>> Professional Support for Apache CouchDB: >>>> https://neighbourhood.ie/couchdb-support/ >>>> >>> >>> -- >>> Professional Support for Apache CouchDB: >>> https://neighbourhood.ie/couchdb-support/ >>> >> >> -- >> Professional Support for Apache CouchDB: >> https://neighbourhood.ie/couchdb-support/ >>
smime.p7s
Description: S/MIME cryptographic signature
