Remove old fauxton clone is src: rm -rf src/fauxton - rebar cannot basically switch dependency origin on fly, only just a branch. That's why it cannot checkout 2601-2390-config-backdoor as it doesn't exists in apache repository. -- ,,,^..^,,,
On Tue, May 5, 2015 at 10:16 AM, Antoine Duchâteau <[email protected]> wrote: > Right, > > I used > > {fauxton, {url, > "https://github.com/robertkowalski/couchdb-fauxton.git"}, {branch, > "2601-2390-config-backdoor"}, [raw]}, > > but I get: > > Updating fauxton from > {git,"https://github.com/robertkowalski/couchdb-fauxton.git";, > {branch,"2601-2390-config-backdoor"}} > error: pathspec '2601-2390-config-backdoor' did not match any file(s) known > to git. > ERROR: sh(git checkout -q 2601-2390-config-backdoor) > failed with return code 1 and the following output: > > Though when I do a > > git clone https://github.com/robertkowalski/couchdb-fauxton.git and git > checkout -q 2601-2390-config-backdoor, the branch exists. > > Any idea ? > A. > > Alexander Shorin > 4 mai 2015 17:33 > > > Just replace "fauxton" with {url, > "https://github.com/robertcowalski/couchdb-faxuton"} > See > https://github.com/apache/couchdb/blob/master/rebar.config.script#L56-L67 > for explanation of how dependency definitions are being handled. > > > -- > ,,,^..^,,, > Alexander Shorin > 4 mai 2015 16:09 > > Here is an awesome link to simplify your searches for opened pull > requests: http://s.apache.org/couchdb-ubersicht > > -- > ,,,^..^,,, > Alexander Shorin > 4 mai 2015 16:06 > > Hi Antoine! > > On Mon, May 4, 2015 at 4:55 PM, Antoine Duchâteau <[email protected]> > wrote: > > I am currently testing CouchDB 2.0 and I am wondering if I do things right. > > Thanks for joining our big couch testing party (: > > I used the master branch from the git to compile CouchDB from sources but I > think I read somewhere that fixes for CouchDB 2.0 where being committed to a > Cassim ? branch. > > You might be references to 2657-fix-cassim-fabric-calls branch, right? > > Should I use this branch instead of master for testing ? Where can it be > found ? > > If you want to test feature branch for some specific subprobject, just > edit rebar.config.script in order to point subproject to that branch > instead of master one. Then run again `./configure` to let rebar fetch > and update source tree and `make` to compile the changed source files. > > But specifically to those cassim branch, afaik the work isn't yet done > on it. Instead, you may check opened pull requests on GitHub for some > subprojects and tests these as they are proposed for merge. > > CouchDB crashed complaining about ulimit -n being to low. What is a sensible > value for ulimit -n ? > > It depends, but if you don't care about, set some big one like 65536 or > nolimit. > > -- > ,,,^..^,,, > > Antoine Duchâteau > 4 mai 2015 15:55 > Hi list, > > I am currently testing CouchDB 2.0 and I am wondering if I do things right. > > I used the master branch from the git to compile CouchDB from sources but I > think I read somewhere that fixes for CouchDB 2.0 where being committed to a > Cassim ? branch. > > Should I use this branch instead of master for testing ? Where can it be > found ? > > CouchDB crashed complaining about ulimit -n being to low. What is a sensible > value for ulimit -n ? > > Thanks in advance, > Antoine
