You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Jan Lehnardt <ja...@apache.org> on 2016/07/13 16:35:58 UTC
Starting 2.0 Release Candidates
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
--
Re: Starting 2.0 Release Candidates
Posted by Andy Wenk <an...@apache.org>.
Hey all,
I installed the tarball and ran CouchDB:
$ ./dev/run
[ * ] Setup environment ... ok
[ * ] Ensure CouchDB is built ... ok
[ * ] Prepare configuration files ... ok
[ * ] Start node node1 ... ok
[ * ] Start node node2 ... ok
[ * ] Start node node3 ... ok
[ * ] Check node at http://127.0.0.1:15984/ ... failed: [Errno socket error] [Errno 61] Connection refused
[ * ] Check node at http://127.0.0.1:25984/ ... ok
[ * ] Check node at http://127.0.0.1:35984/ ... ok
[ * ] Check node at http://127.0.0.1:15984/ ... ok
[ * ] Running cluster setup ... ok
[ * ] Developers cluster is set up at http://127.0.0.1:15984.
Admin username: root
Password: möööp
Time to hack! ...
So everything is fine ;-). Fauxton is cool :D
Mac OS X 10.11.5 (15F34)
Awesome!!
All the best
Andy
--
Andy Wenk
RockIt!
Hamburg / Germany
GPG public key: https://pgp.mit.edu/pks/lookup?op=get&search=0x4F1D0C59BC90917D
> On 14 Jul 2016, at 11:25, Jan Lehnardt <ja...@apache.org> wrote:
>
> Heya Volker,
>
>> On 14 Jul 2016, at 11:20, Volker Mische <vo...@gmail.com> wrote:
>>
>> Hi all,
>>
>> I did run a "make check" all tests passed, except for the JavaScript
>> ones, though I guess that was intended (it prints "HTTP API was disabled
>> at compile time.”).
>
> you can run the JS tests if you do `./configure -c`. *most* of them should work™ ;)
>
>> Linux emil 4.3.0-1-amd64 #1 SMP Debian 4.3.3-5 (2016-01-04) x86_64 GNU/Linux
>> Erlang R16B03-1 (erts-5.10.4.0.0.1) [source-62b74b5] [64-bit] [smp:4:4]
>> [async-threads:10] [hipe] [kernel-poll:false]
>
> Thank you for the report!
>
> Best
> Jan
> -]-
>
>
>>
>> Cheers,
>> Volker
>>
>>
>> On 07/13/2016 06:35 PM, 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/
Re: Starting 2.0 Release Candidates
Posted by Garren Smith <ga...@apache.org>.
Ok. I tested properly this time.
I ran make check twice. The first time a compaction test failed. Second
time only the replication.js test failed.
make build worked and setup worked via Fauxton.
OSX 10.11.5 (15F34)
On Thu, Jul 14, 2016 at 11:25 AM, Jan Lehnardt <ja...@apache.org> wrote:
> Heya Volker,
>
> > On 14 Jul 2016, at 11:20, Volker Mische <vo...@gmail.com> wrote:
> >
> > Hi all,
> >
> > I did run a "make check" all tests passed, except for the JavaScript
> > ones, though I guess that was intended (it prints "HTTP API was disabled
> > at compile time.”).
>
> you can run the JS tests if you do `./configure -c`. *most* of them should
> work™ ;)
>
> > Linux emil 4.3.0-1-amd64 #1 SMP Debian 4.3.3-5 (2016-01-04) x86_64
> GNU/Linux
> > Erlang R16B03-1 (erts-5.10.4.0.0.1) [source-62b74b5] [64-bit] [smp:4:4]
> > [async-threads:10] [hipe] [kernel-poll:false]
>
> Thank you for the report!
>
> Best
> Jan
> -]-
>
>
> >
> > Cheers,
> > Volker
> >
> >
> > On 07/13/2016 06:35 PM, 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/
>
>
Re: Starting 2.0 Release Candidates
Posted by Jan Lehnardt <ja...@apache.org>.
Heya Volker,
> On 14 Jul 2016, at 11:20, Volker Mische <vo...@gmail.com> wrote:
>
> Hi all,
>
> I did run a "make check" all tests passed, except for the JavaScript
> ones, though I guess that was intended (it prints "HTTP API was disabled
> at compile time.”).
you can run the JS tests if you do `./configure -c`. *most* of them should work™ ;)
> Linux emil 4.3.0-1-amd64 #1 SMP Debian 4.3.3-5 (2016-01-04) x86_64 GNU/Linux
> Erlang R16B03-1 (erts-5.10.4.0.0.1) [source-62b74b5] [64-bit] [smp:4:4]
> [async-threads:10] [hipe] [kernel-poll:false]
Thank you for the report!
Best
Jan
-]-
>
> Cheers,
> Volker
>
>
> On 07/13/2016 06:35 PM, 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/
Re: Starting 2.0 Release Candidates
Posted by Volker Mische <vo...@gmail.com>.
Hi all,
I did run a "make check" all tests passed, except for the JavaScript
ones, though I guess that was intended (it prints "HTTP API was disabled
at compile time.").
Linux emil 4.3.0-1-amd64 #1 SMP Debian 4.3.3-5 (2016-01-04) x86_64 GNU/Linux
Erlang R16B03-1 (erts-5.10.4.0.0.1) [source-62b74b5] [64-bit] [smp:4:4]
[async-threads:10] [hipe] [kernel-poll:false]
Cheers,
Volker
On 07/13/2016 06:35 PM, Jan Lehnardt wrote:
> Dear dev@,
>
> it\u2019s 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\u2019t 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
>
Re: Starting 2.0 Release Candidates
Posted by Johannes Jörg Schmidt <sc...@netzmerk.com>.
An update: The Arch linux CouchDB package already did similar things for
the 1.6 package [1] where it patched CouchDB to accept Erlang 18.
Johannes
[1]
https://git.archlinux.org/svntogit/community.git/tree/trunk/erlang18.patch?h=packages/couchdb
On 14.07.2016 12:14, Johannes Jörg Schmidt 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
>>
>
>
Re: Starting 2.0 Release Candidates
Posted by Johannes Jörg Schmidt <sc...@netzmerk.com>.
WOW! That was fast. And it works:
[jo@jolap couchdb]$ ./dev/run
[ * ] Setup environment ... ok
[ * ] Ensure CouchDB is built ... ok
[ * ] Prepare configuration files ... ok
[ * ] Start node node1 ... ok
[ * ] Start node node2 ... ok
[ * ] Start node node3 ... ok
[ * ] Check node at http://127.0.0.1:15984/ ... failed: <urlopen error
[Errno 111] Connection refused>
[ * ] Check node at http://127.0.0.1:25984/ ... ok
[ * ] Check node at http://127.0.0.1:35984/ ... ok
[ * ] Check node at http://127.0.0.1:15984/ ... ok
[ * ] Running cluster setup ... ok
[ * ] Developers cluster is set up at http://127.0.0.1:15984.
[jo@jolap couchdb]$ erl
Erlang/OTP 19 [erts-8.0] [source] [64-bit] [smp:4:4] [async-threads:10]
Thanks!
Johannes
On 14.07.2016 19:04, Robert Newson wrote:
> This is now fixed on master.
>
> Sent from my iPhone
>
>> On 14 Jul 2016, at 14:19, Jan Lehnardt <ja...@apache.org> 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 <jo...@netzmerk.com> 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/
>>
>
Re: Starting 2.0 Release Candidates
Posted by Alexander Shorin <kx...@gmail.com>.
On Fri, Jul 15, 2016 at 3:19 PM, Constantin Teodorescu
<br...@gmail.com> wrote:
> Just wanted to know where are (in 2.0 release) the old files:
>
> - _utils/script/jquery.couch.js
> - _utils/script/base64.js
> - _utils/script/sha1.js
> - _utils/script/json2.js
>
> I'm using *jquery.couch.js* in a lot of applications completely hosted on
> CouchDB 1.6 and I want to test them against 2.0 release!
jquery.couch.js left unmaintained for now, it's not ready for 2.0 and
Fauxton doesn't uses it, so CouchDB doesn't ships it or it
dependencies anymore.
Copying into your project sounds as good idea.
--
,,,^..^,,,
Re: Starting 2.0 Release Candidates
Posted by Jan Lehnardt <ja...@apache.org>.
> On 15 Jul 2016, at 14:19, Constantin Teodorescu <br...@gmail.com> wrote:
>
> On Thu, Jul 14, 2016 at 11:55 PM, Jan Lehnardt <ja...@apache.org> wrote:
>
>> New tarball with the changes here:
>>
>>
>> https://home.apache.org/~jan/couchdb/2.0/RC/apache-couchdb-2.0.0-2dddaf0.tar.gz
>>
>> untar, ./configure, make ./dev/run , everything is working OK on Ubuntu
> 15.10 and 16.04 64 bit!!!!
>
> Just wanted to know where are (in 2.0 release) the old files:
>
> - _utils/script/jquery.couch.js
> - _utils/script/base64.js
> - _utils/script/sha1.js
> - _utils/script/json2.js
>
> I'm using *jquery.couch.js* in a lot of applications completely hosted on
> CouchDB 1.6 and I want to test them against 2.0 release!
>
> For the moment I just copied "*jquery.couch.js*" file in my project and it
> worked but I just wanted to know if those files will be supplied in 2.0
> official package.
I’d recommend to copy all files you need and put them into your project.
Best
Jan
--
>
> Teo
--
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/
Re: Starting 2.0 Release Candidates
Posted by Constantin Teodorescu <br...@gmail.com>.
On Thu, Jul 14, 2016 at 11:55 PM, Jan Lehnardt <ja...@apache.org> wrote:
> New tarball with the changes here:
>
>
> https://home.apache.org/~jan/couchdb/2.0/RC/apache-couchdb-2.0.0-2dddaf0.tar.gz
>
> untar, ./configure, make ./dev/run , everything is working OK on Ubuntu
15.10 and 16.04 64 bit!!!!
Just wanted to know where are (in 2.0 release) the old files:
- _utils/script/jquery.couch.js
- _utils/script/base64.js
- _utils/script/sha1.js
- _utils/script/json2.js
I'm using *jquery.couch.js* in a lot of applications completely hosted on
CouchDB 1.6 and I want to test them against 2.0 release!
For the moment I just copied "*jquery.couch.js*" file in my project and it
worked but I just wanted to know if those files will be supplied in 2.0
official package.
Teo
Re: Starting 2.0 Release Candidates
Posted by Clemens Stolle <cl...@fastmail.com>.
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 <cl...@fastmail.com>:
>
> 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 <ja...@apache.org> 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 <ja...@apache.org> 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 <rn...@apache.org> wrote:
>>>>>
>>>>> This is now fixed on master.
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>>> On 14 Jul 2016, at 14:19, Jan Lehnardt <ja...@apache.org> 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 <jo...@netzmerk.com> 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/
>>
Re: Starting 2.0 Release Candidates
Posted by Clemens Stolle <cl...@fastmail.com>.
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 <ja...@apache.org> 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 <ja...@apache.org> 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 <rn...@apache.org> wrote:
> >>>
> >>> This is now fixed on master.
> >>>
> >>> Sent from my iPhone
> >>>
> >>>> On 14 Jul 2016, at 14:19, Jan Lehnardt <ja...@apache.org> 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 <jo...@netzmerk.com> 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/
>
Re: Starting 2.0 Release Candidates
Posted by Jan Lehnardt <ja...@apache.org>.
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 <ja...@apache.org> 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 <ja...@apache.org> 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 <rn...@apache.org> wrote:
>>>
>>> This is now fixed on master.
>>>
>>> Sent from my iPhone
>>>
>>>> On 14 Jul 2016, at 14:19, Jan Lehnardt <ja...@apache.org> 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 <jo...@netzmerk.com> 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/
Re: Starting 2.0 Release Candidates
Posted by Jan Lehnardt <ja...@apache.org>.
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 <ja...@apache.org> 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 <rn...@apache.org> wrote:
>>
>> This is now fixed on master.
>>
>> Sent from my iPhone
>>
>>> On 14 Jul 2016, at 14:19, Jan Lehnardt <ja...@apache.org> 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 <jo...@netzmerk.com> 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/
Re: Starting 2.0 Release Candidates
Posted by Jan Lehnardt <ja...@apache.org>.
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 <rn...@apache.org> wrote:
>
> This is now fixed on master.
>
> Sent from my iPhone
>
>> On 14 Jul 2016, at 14:19, Jan Lehnardt <ja...@apache.org> 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 <jo...@netzmerk.com> 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/
Re: Starting 2.0 Release Candidates
Posted by Robert Newson <rn...@apache.org>.
This is now fixed on master.
Sent from my iPhone
> On 14 Jul 2016, at 14:19, Jan Lehnardt <ja...@apache.org> 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 <jo...@netzmerk.com> 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/
>
Re: Starting 2.0 Release Candidates
Posted by Jan Lehnardt <ja...@apache.org>.
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 <jo...@netzmerk.com> 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/
Re: Starting 2.0 Release Candidates
Posted by Johannes Jörg Schmidt <jo...@netzmerk.com>.
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
>
Re: Starting 2.0 Release Candidates
Posted by Jan Lehnardt <ja...@apache.org>.
Thanks Garren!
Which OS/Erlang version etc. are you running on?
Also, mind doing one more thing:
make build
cd rel/couchdb
./bin/couchdb
This starts a raw node without cluster setup. Then go to Fauxton and go through the cluster setup screen, and see if things are still fine?
Thank you! :)
Best
Jan
--
> On 14 Jul 2016, at 09:43, Garren Smith <ga...@apache.org> wrote:
>
> This is so exciting.
>
> I've downloaded the tarball and did a ./configure and make. Then I ran
> /dev/run
> Everything worked nicely. The Fauxton verify install worked as well.
>
> On Wed, Jul 13, 2016 at 9:18 PM, Andy Wenk <an...@apache.org> wrote:
>
>> Yeah - awesome news. I will try to find a free time slot and try the
>> tarball.
>>
>> Excited! Thanks so much to everyone making this happening!
>>
>> All the best
>>
>> Andy
>>
>> --
>> Andy Wenk
>> RockIt!
>>
>> Hamburg / Germany
>>
>> GPG public key:
>> https://pgp.mit.edu/pks/lookup?op=get&search=0x4F1D0C59BC90917D
>>
>>> On 13 Jul 2016, at 18:58, Jan Lehnardt <ja...@apache.org> wrote:
>>>
>>>
>>>> On 13 Jul 2016, at 18:35, Jan Lehnardt <ja...@apache.org> 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)
>>>
>>> quick update: turns out, the docker bits are an option too.
>> couchdb-docker (https://github.com/klaemo/docker-couchdb thanks @klaemo!
>> <3) track master (at least 2.0-dev), so you can use that for testing as
>> well.
>>>
>>> Clemens, a 2.0RC1 tag should appear shortly, wanna update the 2.0-single
>> one for that?
>>>
>>> Best
>>> Jan
>>> --
>>>
>>>
>>>> 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/
Re: Starting 2.0 Release Candidates
Posted by Garren Smith <ga...@apache.org>.
This is so exciting.
I've downloaded the tarball and did a ./configure and make. Then I ran
/dev/run
Everything worked nicely. The Fauxton verify install worked as well.
On Wed, Jul 13, 2016 at 9:18 PM, Andy Wenk <an...@apache.org> wrote:
> Yeah - awesome news. I will try to find a free time slot and try the
> tarball.
>
> Excited! Thanks so much to everyone making this happening!
>
> All the best
>
> Andy
>
> --
> Andy Wenk
> RockIt!
>
> Hamburg / Germany
>
> GPG public key:
> https://pgp.mit.edu/pks/lookup?op=get&search=0x4F1D0C59BC90917D
>
> > On 13 Jul 2016, at 18:58, Jan Lehnardt <ja...@apache.org> wrote:
> >
> >
> >> On 13 Jul 2016, at 18:35, Jan Lehnardt <ja...@apache.org> 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)
> >
> > quick update: turns out, the docker bits are an option too.
> couchdb-docker (https://github.com/klaemo/docker-couchdb thanks @klaemo!
> <3) track master (at least 2.0-dev), so you can use that for testing as
> well.
> >
> > Clemens, a 2.0RC1 tag should appear shortly, wanna update the 2.0-single
> one for that?
> >
> > Best
> > Jan
> > --
> >
> >
> >> 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/
> >
>
>
Re: Starting 2.0 Release Candidates
Posted by Andy Wenk <an...@apache.org>.
Yeah - awesome news. I will try to find a free time slot and try the tarball.
Excited! Thanks so much to everyone making this happening!
All the best
Andy
--
Andy Wenk
RockIt!
Hamburg / Germany
GPG public key: https://pgp.mit.edu/pks/lookup?op=get&search=0x4F1D0C59BC90917D
> On 13 Jul 2016, at 18:58, Jan Lehnardt <ja...@apache.org> wrote:
>
>
>> On 13 Jul 2016, at 18:35, Jan Lehnardt <ja...@apache.org> 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)
>
> quick update: turns out, the docker bits are an option too. couchdb-docker (https://github.com/klaemo/docker-couchdb thanks @klaemo! <3) track master (at least 2.0-dev), so you can use that for testing as well.
>
> Clemens, a 2.0RC1 tag should appear shortly, wanna update the 2.0-single one for that?
>
> Best
> Jan
> --
>
>
>> 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/
>
Re: Starting 2.0 Release Candidates
Posted by Jan Lehnardt <ja...@apache.org>.
> On 13 Jul 2016, at 18:35, Jan Lehnardt <ja...@apache.org> 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)
quick update: turns out, the docker bits are an option too. couchdb-docker (https://github.com/klaemo/docker-couchdb thanks @klaemo! <3) track master (at least 2.0-dev), so you can use that for testing as well.
Clemens, a 2.0RC1 tag should appear shortly, wanna update the 2.0-single one for that?
Best
Jan
--
> 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/
Re: Starting 2.0 Release Candidates
Posted by Robert Newson <rn...@apache.org>.
Hurray! :)
Sent from my iPhone
> On 13 Jul 2016, at 17:35, Jan Lehnardt <ja...@apache.org> 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
> --
>