On Fri, Nov 26, 2010 at 7:14 AM, Peter Lemenkov wrote:
> 2010/11/26 Robert Newson :
>> pretty sure ibrowse and mochiweb have important tweaks, using versions
>> without them is broken.
>
> I'm not sure about mochiweb (since couchdb contains very old svn
> snapshot, and it's hard to check for the d
On Fri, Nov 26, 2010 at 00:27, Robert Newson wrote:
> pretty sure ibrowse and mochiweb have important tweaks, using versions
> without them is broken.
Are these being pushed upstream?
Cheers,
Dirkjan
+1
* Md5 sum matches
* make dist works
* Browser tests tested on FF and Chromium
* my system:
* Debian
* AMD64
* Erlang R13B04
* SpiderMonkey 1.9.1.9
* FF (IceWeasel) 3.6.4
* Chromimum 6.0.420.0 (48550)
On 11/25/2010 07:43 PM, Paul Davis wrote:
> Hello,
>
> I would like call a vote f
2010/11/26 Dirkjan Ochtman :
> On Fri, Nov 26, 2010 at 00:27, Robert Newson wrote:
>> pretty sure ibrowse and mochiweb have important tweaks, using versions
>> without them is broken.
>
> Are these being pushed upstream?
Unfortunately, right now CouchDB's own copy of mochiweb misses many
bugfixes
On Fri, Nov 26, 2010 at 11:30, Peter Lemenkov wrote:
> Much better scenario would be to disallow generally bad practice of
> bundling sources from different projects, but this would be painful
> because even many popular Linux distributions (not to mention of Mac
> OS X and Windoze) lacks of good
On Thu, Nov 25, 2010 at 19:43, Paul Davis wrote:
> We encourage the whole community to download and test these release artifacts
> so
> that any critical issues can be resolved before the release is made. Everyone
> is
> free to vote on this release, so get stuck in!
>
> We are voting on the fol
On Fri, Nov 26, 2010 at 11:30 AM, Peter Lemenkov wrote:
> Unfortunately, right now CouchDB's own copy of mochiweb misses many
> bugfixes already available in upstream. So it's worth to rebase
> couchdb on top of recently released 1.4.1 rather than trying to find
> something valuable in src/mochiw
2010/11/26 Benoit Chesneau :
> On Fri, Nov 26, 2010 at 11:30 AM, Peter Lemenkov wrote:
>
>> Unfortunately, right now CouchDB's own copy of mochiweb misses many
>> bugfixes already available in upstream. So it's worth to rebase
>> couchdb on top of recently released 1.4.1 rather than trying to find
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Cohnen updated COUCHDB-968:
-
Affects Version/s: 1.0
> Duplicated IDs in _all_docs
> ---
>
>
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 1.0.1, 1.0.2
On Fri, Nov 26, 2010 at 11:59 AM, Peter Lemenkov wrote:
> 2010/11/26 Benoit Chesneau :
>> On Fri, Nov 26, 2010 at 11:30 AM, Peter Lemenkov wrote:
>>
>>> Unfortunately, right now CouchDB's own copy of mochiweb misses many
>>> bugfixes already available in upstream. So it's worth to rebase
>>> couc
On 26 Nov 2010, at 11:34, Dirkjan Ochtman wrote:
> On Fri, Nov 26, 2010 at 11:30, Peter Lemenkov wrote:
>> Much better scenario would be to disallow generally bad practice of
>> bundling sources from different projects, but this would be painful
>> because even many popular Linux distributions (
On Fri, Nov 26, 2010 at 6:14 AM, Peter Lemenkov wrote:
> 2010/11/26 Robert Newson :
>> pretty sure ibrowse and mochiweb have important tweaks, using versions
>> without them is broken.
>
> I'm not sure about mochiweb (since couchdb contains very old svn
> snapshot, and it's hard to check for the d
On 26 Nov 2010, at 11:30, Peter Lemenkov wrote:
> 2010/11/26 Dirkjan Ochtman :
>> On Fri, Nov 26, 2010 at 00:27, Robert Newson wrote:
>>> pretty sure ibrowse and mochiweb have important tweaks, using versions
>>> without them is broken.
>>
>> Are these being pushed upstream?
>
> Unfortunately,
On Fri, Nov 26, 2010 at 12:55, Jan Lehnardt wrote:
> This breaks the basic requirement of not requiring networks access for
> an installation which I remember Noah is advocating.
Well, with doing it in the build system I really meant something that
pulls them in for the tarball (or a tarball -- h
for mochiweb at least one important tweak was in mochijson2.erl
(COUCHDB-796). Using a mochiweb without this fix undoes a resolved
ticket. Additionally I had to do some extra work to get the HTTPS
support working (though it's more than possible that this was also
fixed upstream since I upgraded; I
On 26 Nov 2010, at 13:22, Dirkjan Ochtman wrote:
> On Fri, Nov 26, 2010 at 12:55, Jan Lehnardt wrote:
>> This breaks the basic requirement of not requiring networks access for
>> an installation which I remember Noah is advocating.
>
> Well, with doing it in the build system I really meant some
On Fri, Nov 26, 2010 at 13:53, Robert Newson wrote:
> Obivously I agree we should be using official releases of mochiweb and
> ibrowse but that's not the case today, discarding the patches can
> potentially break CouchDB. I don't like it, but the fact that part of
> our source tree is imported fro
On 26 Nov 2010, at 14:23, Dirkjan Ochtman wrote:
> On Fri, Nov 26, 2010 at 13:53, Robert Newson wrote:
>> Obivously I agree we should be using official releases of mochiweb and
>> ibrowse but that's not the case today, discarding the patches can
>> potentially break CouchDB. I don't like it, but
On Fri, Nov 26, 2010 at 14:32, Jan Lehnardt wrote:
> Understandable. We could make things clearer in CHANGES.
That would be much appreciated.
Cheers,
Dirkjan
On 26 Nov 2010, at 07:14, Peter Lemenkov wrote:
> 2010/11/26 Robert Newson :
>> pretty sure ibrowse and mochiweb have important tweaks, using versions
>> without them is broken.
>
> I'm not sure about mochiweb (since couchdb contains very old svn
> snapshot, and it's hard to check for the differ
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Cohnen updated COUCHDB-968:
-
Description:
We have a database, which is causing serious trouble with compaction and
r
Hello
2010/11/26 Jan Lehnardt :
> We always patch Mochiweb to fit our needs that are divergent from the
> upstream project. It isn't safe to assume an independent cut of Mochiweb
> will just work.
Well, it isn't even safe to assume that it will work on an arbitrary
system with different set of u
2010/11/26 Peter Lemenkov :
> just play for the stable API/ABI interfaces. Shipping internally a
s,play,play,
--
With best regards, Peter Lemenkov.
2010/11/26 Peter Lemenkov :
> 2010/11/26 Peter Lemenkov :
>> just play for the stable API/ABI interfaces. Shipping internally a
>
> s,play,play,
s,play,pRay,
:)
--
With best regards, Peter Lemenkov.
On 26 Nov 2010, at 15:23, Peter Lemenkov wrote:
> Hello
>
> 2010/11/26 Jan Lehnardt :
>
>> We always patch Mochiweb to fit our needs that are divergent from the
>> upstream project. It isn't safe to assume an independent cut of Mochiweb
>> will just work.
>
> Well, it isn't even safe to assume
On Fri, Nov 26, 2010 at 15:57, Jan Lehnardt wrote:
> I wonder what the best solution here is. The problem with updating
> to the latest Mochiweb right before a release is that subtle issues
> don't have time surfacing in trunk. To ensure stable releases we
> should be conservative with updates (mo
I'm working on a branch to use mochiweb 1.4.1 in trunk for a the 1.2 release.
b.
On Fri, Nov 26, 2010 at 3:06 PM, Dirkjan Ochtman wrote:
> On Fri, Nov 26, 2010 at 15:57, Jan Lehnardt wrote:
>> I wonder what the best solution here is. The problem with updating
>> to the latest Mochiweb right bef
On Thu, Nov 25, 2010 at 7:43 PM, Paul Davis wrote:
[ ... ]
> We are voting on the following release artifacts:
>
> http://people.apache.org/~davisp/dist/1.0.2/
>
[one of my older production servers]
FreeBSD 6.x/i386
Erlang R13B04
Spidermonkey 1.7.x
gmake check = great success
[in a virtualbox]
[
https://issues.apache.org/jira/browse/COUCHDB-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12936049#action_12936049
]
Jan Lehnardt commented on COUCHDB-798:
--
I made a bunch of more tests, this time from
[
https://issues.apache.org/jira/browse/COUCHDB-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12936056#action_12936056
]
Rachel Willmer commented on COUCHDB-763:
I think I am encountering this problem wi
FYI: I've updated couchdb to mochiweb 1.4.1 on a branch called mochiweb-1.4.1.
The only tweaks are to replace Makefile with our Makefile.am and to
retain our mochiweb.app.in (with updated vsn).
I've verified that Futon tests work, that the integer fix is
incorporated and that https support still
[
https://issues.apache.org/jira/browse/COUCHDB-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Lehnardt closed COUCHDB-798.
Resolution: Fixed
> Compile mochijson2 down to native code
> -
Hi all, there's a discussion in the 1.0.2 voting thread about better tracking
of upstream dependencies like mochiweb. One point that keeps getting brought
up is that build systems should not need network access. Is that a rule which
applies to building from an SCM repo, or only to builds of re
The release artefact absolutely should not, ever, pull down files from the
network. However, I can see a way forward by having the bootstrap script manage
the bundling of external dependancies. The bootstrap script should only ever be
run from a checkout of the code. Whatever it downloaded and p
On Fri, Nov 26, 2010 at 21:44, Noah Slater wrote:
> But assuming we got this working, we face the problem of not being able to
> apply our own patches. Also, the software it downloads might have some bug in
> it that was introduced a week, day, or hour before the release was made. How
> would w
E.g. for packaging on distros like FreeBSD you usually download the
the software in an unmodified state from an official mirror [of the
software] and then patch it before building and registering the
install.
So e.g., I'd download CouchDB from an apache mirror and then patch
whatever I need and th
On 26 Nov 2010, at 20:58, Dirkjan Ochtman wrote:
> On Fri, Nov 26, 2010 at 21:44, Noah Slater wrote:
>> But assuming we got this working, we face the problem of not being able to
>> apply our own patches. Also, the software it downloads might have some bug
>> in it that was introduced a week,
On Fri, Nov 26, 2010 at 9:02 PM, till wrote:
>
> How often does it happen that CouchDB has to patch/modify software
> like Mochiweb? And what are the chances to push the patches to
> upstream prior to releasing CouchDB. I realize this could slow down
> the release process, but it would make a clea
On Nov 26, 2010, at 3:58 PM, Dirkjan Ochtman wrote:
> On Fri, Nov 26, 2010 at 21:44, Noah Slater wrote:
>> But assuming we got this working, we face the problem of not being able to
>> apply our own patches. Also, the software it downloads might have some bug
>> in it that was introduced a week
On Fri, Nov 26, 2010 at 22:15, Noah Slater wrote:
> If we have a checksum, what's the point?
>
> Why not just include the original source the checksum is taken from?
The point is keeping very exact track of what the source is. And the
point is making it easy for distributors to build without the
On Fri, Nov 26, 2010 at 8:41 PM, wrote:
> Author: jchris
> Date: Sat Nov 27 04:41:20 2010
> New Revision: 1039619
>
> URL: http://svn.apache.org/viewvc?rev=1039619&view=rev
> Log:
> rename "readers" to "members" in _security object, keep backwards
> compatibility with old security objects"
I'v
42 matches
Mail list logo
