You are not logged in.
I have some concerns regarding the CouchDB community package.
If we look through the SVN repository we see the maintainers have followed the actual release of the official team pretty much to the tee
http://couchdb.apache.org/downloads.html
So whilst Ubuntu has been on 1.0.2 we have had 1.1.0 etc within days of being announced.
CouchDB releases are pretty solid (with the exception of a race condition in 1.0.0)
Howver it seems for some unknown reason the last update to the package has been taken out the blue from somewhere on the SVN trunk of CouchDB. The CouchDB team will accept that it is no secret that this release is full of critical bugs. In my case it even vommits on CommonJS stuff (requires on _list and _shows).
When I thought we were living on the edge I thought that this meant as something was released we get same-day/within days, and this seems to be patterned followed before, but for some strange reason its different this time. We have gone to 1.0.1, 1.0.3, 1.1.0, 1.1.0.1 to 1.1.0.342343-svn (actually branded as 1.2 - totally a WIP)
Accepted: obviously deciding weather the follow releases or the tee of the SVN trunk is dependent on the package but with CouchDB it seems we have pick and choose at the drop of a hat.
Do we live on edge by pumping out packages that seg fault just because its at the tip of the svn trunk or latest git commit?
How can I volunteer to do some QA first before stuff moves from community-testing to community?
Last edited by mattopenstack (2011-08-09 05:36:03)
Offline
My understanding is that it is either that version or none at all. The released versions do not build against "js" and we no longer have spidermonkey in the repos.
Offline
Allan. I managed to get 1.1.0 by remove js and installing spidermonkey.
My point is 1.1.0 release is very new still, but it is tested and it works, its what I would call "edge" in the CouchDB community and its what we should be on following the Arch mantra, instead of this nasty 1.1.0x-svn which is actually 1.2. Other distros are on 1.0.1-1.0.3 (the latter at a push).
What else depends on 'js' that it was decided to remove 'spidermonkey' and sod it just build latest couchdb svn to suit this, hey 'it compiles' and basic queries on Futon work so that will do.. Are you sure the removal of spidermonkey wasnt just due to this jump. Isnt spidermonkey and js the same just different version
1.1.0.*-svn (branded 1.2) is not fit for any consumption. Im just shocked that they jumped the package up to that for whatever reason 'dependency or not'
Last edited by mattopenstack (2011-08-09 10:41:14)
Offline
File a bug report. Although I guess the solution will be to remove it from the repo completely.
Offline
@mattopenstack, I have to agree. I cannot successfully run the test suite, or replicate a local db to cloudant. What is the bug status?
update: Gnome3 requires js package.
Last edited by bsquared (2011-09-25 16:34:28)
(c}
Offline
@mattopenstack agreed, Apache CouchDB fully admits to not keeping the branch in a releasable state between releases so taking random commits is a very bad idea. I saw CouchDB 1.2 (the actual release) has been added to community-testing, so hopefully we'll be on a proper release soon.
Sorry to revive an old thread, but I wanted to share my workaround as it could be very useful to the people participating. I've recently updated a project called build-couchdb (from Iris Couch) to work with Arch Linux. This is by far the easiest way to get self contained builds of CouchDB (including their own compiled dependencies). I work with CouchDB every day and often have to run multiple versions to test compatibility and check bug reports, rather than running a VM I use build-couchdb to create self-contained CouchDB instances at various versions. I can then run them as a regular user by just doing ./bin/couchdb in the directory for the version I'd like to run.
See the project here:
https://github.com/iriscouch/build-couchdb
It doesn't mention Arch in the README because I only added support recently - If anyone has problems please add an issue on GitHub. If it works then let me know too and I'll update the README to include Arch.
Offline