Re: [RELEASE][REQUEST] Binaries for 1.3.1-rc.2
T hanks Dave - fully relaxed here on Win7 Ultimate 64 bit. Nick On 18 June 2013 12:45, Dave Cottlehuber wrote: > On 14 June 2013 15:30, Noah Slater wrote: > > Cool. Thanks. I am on vacation until Tues. Is anyone else able to prepare > > Win binaries? > > Done! > > https://dist.apache.org/repos/dist/dev/couchdb/binary/win/1.3.1/rc.2/ > > To test: > - download > - check sigs (like > http://wiki.apache.org/couchdb/Test_procedure#Verifying_the_Candidate) > - run the exe > - launch Apache CouchDB from start menu > - Run “Verify Installation” > - Relax > A+ > Dave >
[jira] [Commented] (COUCHDB-1824) Official documentation of replication algorithm?
[ https://issues.apache.org/jira/browse/COUCHDB-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686861#comment-13686861 ] Jens Alfke commented on COUCHDB-1824: - My latest docs are at https://github.com/couchbase/couchbase-lite-ios/wiki/Replication-Algorithm Feel free to reuse any of that text. > Official documentation of replication algorithm? > > > Key: COUCHDB-1824 > URL: https://issues.apache.org/jira/browse/COUCHDB-1824 > Project: CouchDB > Issue Type: Bug > Components: Documentation >Reporter: Nathan Vander Wilt > > Though it's in some ways an internal detail, it might be nice to provide a > canonical description of CouchDB's replication protocol (algorithm, really) > in the documentation. See links at: > http://wiki.apache.org/couchdb/Replication#Protocol_Documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1824) Official documentation of replication algorithm?
[ https://issues.apache.org/jira/browse/COUCHDB-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686875#comment-13686875 ] Benoit Chesneau commented on COUCHDB-1824: -- I would also love to have any critics of this document which try to describe an implementation of the replication in pseudo code: https://github.com/refuge/rcouch/wiki/Replication-Algorithm > Official documentation of replication algorithm? > > > Key: COUCHDB-1824 > URL: https://issues.apache.org/jira/browse/COUCHDB-1824 > Project: CouchDB > Issue Type: Bug > Components: Documentation >Reporter: Nathan Vander Wilt > > Though it's in some ways an internal detail, it might be nice to provide a > canonical description of CouchDB's replication protocol (algorithm, really) > in the documentation. See links at: > http://wiki.apache.org/couchdb/Replication#Protocol_Documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: git commit: updated refs/heads/1832-fix-empty-attachment-name to 6b8fc08
This should go into 1.2.x., 1.3.x and master.
Sorry for the commit-spam earlier.
Best
Jan
--
On Jun 18, 2013, at 16:59 , j...@apache.org wrote:
> Updated Branches:
> refs/heads/1832-fix-empty-attachment-name [created] 6b8fc0831
>
>
> Prevent creation of empty attachment names via inline API.
>
> It is possible to create an attachment using the inline
> attachment API that has the empty string "" as the name:
>
> {
> "_id":"11612aba0238dc0dd8c2d37e7909b4e6",
> "_attachments": {
>"": {...}
> }
> }
>
> Attachments created this way can’t be retrieved via the
> standalone attachment API.
>
> This patch adds testing for the empty string in the
> `validate_attachment_name` function.
>
> Closes COUCHDB-1832
>
>
> Project: http://git-wip-us.apache.org/repos/asf/couchdb/repo
> Commit: http://git-wip-us.apache.org/repos/asf/couchdb/commit/6b8fc083
> Tree: http://git-wip-us.apache.org/repos/asf/couchdb/tree/6b8fc083
> Diff: http://git-wip-us.apache.org/repos/asf/couchdb/diff/6b8fc083
>
> Branch: refs/heads/1832-fix-empty-attachment-name
> Commit: 6b8fc0831810442ddb23808ab54340fe18f37e8b
> Parents: 0bb6787
> Author: Jan Lehnardt
> Authored: Tue Jun 18 16:28:30 2013 +0200
> Committer: Jan Lehnardt
> Committed: Tue Jun 18 16:33:49 2013 +0200
>
> --
> share/www/script/test/attachment_names.js | 19 +++
> src/couchdb/couch_httpd_db.erl| 2 ++
> 2 files changed, 21 insertions(+)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/couchdb/blob/6b8fc083/share/www/script/test/attachment_names.js
> --
> diff --git a/share/www/script/test/attachment_names.js
> b/share/www/script/test/attachment_names.js
> index c9a5fcc..b140f0b 100644
> --- a/share/www/script/test/attachment_names.js
> +++ b/share/www/script/test/attachment_names.js
> @@ -48,6 +48,25 @@ couchTests.attachment_names = function(debug) {
> resp = db.save(binAttDoc);
> TEquals(true, resp.ok, "attachment_name: inline attachment");
>
> + // COUCHDB-1832 Inline Attachment API allows empty names
> + var binAttDoc4 = {
> +_id: "bin_doc4",
> +_attachments:{
> + "": {
> +content_type:"text/plain",
> +data: "VGhpcyBpcyBhIGJhc2U2NCBlbmNvZGVkIHRleHQ="
> + }
> +}
> + };
> +
> + try {
> +resp = db.save(binAttDoc4);
> +TEquals(1,2, "should throw on empty attachment names");
> + } catch (e) {
> +TEquals(e.error, "bad_request", "should return bad_request");
> +TEquals(e.reason, "Attachment name can't be empty",
> +"should state that attachment name can't be empty");
> + }
>
> // standalone docs
> var bin_data = "JHAPDO*AU£PN ){(3u[d 93DQ9¡€])}
> ææøo'∂ƒæ≤çæππ•¥∫¶®#†π¶®¥π€ª®˙π8np";
>
> http://git-wip-us.apache.org/repos/asf/couchdb/blob/6b8fc083/src/couchdb/couch_httpd_db.erl
> --
> diff --git a/src/couchdb/couch_httpd_db.erl b/src/couchdb/couch_httpd_db.erl
> index f270fef..9a5af0f 100644
> --- a/src/couchdb/couch_httpd_db.erl
> +++ b/src/couchdb/couch_httpd_db.erl
> @@ -1198,6 +1198,8 @@ validate_attachment_name(Name) when is_list(Name) ->
> validate_attachment_name(list_to_binary(Name));
> validate_attachment_name(<<"_",_/binary>>) ->
> throw({bad_request, <<"Attachment name can't start with '_'">>});
> +validate_attachment_name(<<"">>) ->
> +throw({bad_request, <<"Attachment name can't be empty">>});
> validate_attachment_name(Name) ->
> case couch_util:validate_utf8(Name) of
> true -> Name;
>
[jira] [Commented] (COUCHDB-1832) Inline Attachment API allows empty names
[
https://issues.apache.org/jira/browse/COUCHDB-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686801#comment-13686801
]
ASF subversion and git services commented on COUCHDB-1832:
--
Commit 6b8fc0831810442ddb23808ab54340fe18f37e8b in branch
refs/heads/1832-fix-empty-attachment-name from [~janl]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=6b8fc08 ]
Prevent creation of empty attachment names via inline API.
It is possible to create an attachment using the inline
attachment API that has the empty string "" as the name:
{
"_id":"11612aba0238dc0dd8c2d37e7909b4e6",
"_attachments": {
"": {...}
}
}
Attachments created this way can’t be retrieved via the
standalone attachment API.
This patch adds testing for the empty string in the
`validate_attachment_name` function.
Closes COUCHDB-1832
> Inline Attachment API allows empty names
>
>
> Key: COUCHDB-1832
> URL: https://issues.apache.org/jira/browse/COUCHDB-1832
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
>Reporter: Jan Lehnardt
>
> The standalone attachment API allows the creation of attachments with an
> empty name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1449) Couchdb returns stopped status before process exits
[ https://issues.apache.org/jira/browse/COUCHDB-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686784#comment-13686784 ] ASF subversion and git services commented on COUCHDB-1449: -- Commit b5d18fe2ae456d1fea9fd3e3990ccabf815326c2 in branch refs/heads/1832-fix-empty-attachment-name from [~wendall911] [ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=b5d18fe ] Added comment for COUCHDB-1449, and added sections for 1.2.2 to CHANGES > Couchdb returns stopped status before process exits > --- > > Key: COUCHDB-1449 > URL: https://issues.apache.org/jira/browse/COUCHDB-1449 > Project: CouchDB > Issue Type: Bug >Affects Versions: 1.2, 1.3 > Environment: *NIX >Reporter: Wendall Cada >Assignee: Wendall Cada >Priority: Blocker > Labels: patch > Fix For: 1.2.2, 1.3 > > Attachments: COUCHDB-1449-wait-for-process-exit.patch > > > When restarting couchdb via init script, couchdb returns success status > before the process is exited. When a start is issued before the process ends, > couchdb fails to start, but returns success. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1832) Inline Attachment API allows empty names
[
https://issues.apache.org/jira/browse/COUCHDB-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686783#comment-13686783
]
ASF subversion and git services commented on COUCHDB-1832:
--
Commit ad774b6e096d5011a16837e600db70204e9ae28c in branch
refs/heads/1832-fix-empty-attachment-name from [~janl]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=ad774b6 ]
Prevent creation of empty attachment names via inline API.
It is possible to create an attachment using the inline
attachment API that has the empty string "" as the name:
{
"_id":"11612aba0238dc0dd8c2d37e7909b4e6",
"_attachments": {
"": {...}
}
}
Attachments created this way can’t be retrieved via the
standalone attachment API.
This patch adds testing for the empty string in the
`validate_attachment_name` function.
Closes COUCHDB-1832
> Inline Attachment API allows empty names
>
>
> Key: COUCHDB-1832
> URL: https://issues.apache.org/jira/browse/COUCHDB-1832
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
>Reporter: Jan Lehnardt
>
> The standalone attachment API allows the creation of attachments with an
> empty name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1832) Inline Attachment API allows empty names
Jan Lehnardt created COUCHDB-1832: - Summary: Inline Attachment API allows empty names Key: COUCHDB-1832 URL: https://issues.apache.org/jira/browse/COUCHDB-1832 Project: CouchDB Issue Type: Bug Components: HTTP Interface Reporter: Jan Lehnardt The standalone attachment API allows the creation of attachments with an empty name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COUCHDB-1831) Clearing AutoSession cookie doesn't respect domain value, fails to clear domain = '.example.com' values
[ https://issues.apache.org/jira/browse/COUCHDB-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pauli Price updated COUCHDB-1831: - Summary: Clearing AutoSession cookie doesn't respect domain value, fails to clear domain = '.example.com' values (was: Clearing AutoSession cooking doesn't respect domain value, fails to clear domain = '.example.com' values) > Clearing AutoSession cookie doesn't respect domain value, fails to clear > domain = '.example.com' values > --- > > Key: COUCHDB-1831 > URL: https://issues.apache.org/jira/browse/COUCHDB-1831 > Project: CouchDB > Issue Type: Bug >Reporter: Pauli Price > > Working on a remote authentication server. Setting AuthSession cookie at the > domain level - i.e. couchdb running at db.example.com & auth server running > at auth.example.com -- set cookie with domain='.example.com' & visit > db.example.com/_utils --- session is logged in. Click 'logout' in futon, > user remains logged in. Examine cookies -- two AuthSession cookies exist -- > one with domain = 'db.example.com' with blank value, and the original one > with domain='.example.com' -- unchanged. > Fix is to pass the original cookie's domain value into the set cookie > statement that clears the session. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1831) Clearing AutoSession cooking doesn't respect domain value, fails to clear domain = '.example.com' values
Pauli Price created COUCHDB-1831: Summary: Clearing AutoSession cooking doesn't respect domain value, fails to clear domain = '.example.com' values Key: COUCHDB-1831 URL: https://issues.apache.org/jira/browse/COUCHDB-1831 Project: CouchDB Issue Type: Bug Reporter: Pauli Price Working on a remote authentication server. Setting AuthSession cookie at the domain level - i.e. couchdb running at db.example.com & auth server running at auth.example.com -- set cookie with domain='.example.com' & visit db.example.com/_utils --- session is logged in. Click 'logout' in futon, user remains logged in. Examine cookies -- two AuthSession cookies exist -- one with domain = 'db.example.com' with blank value, and the original one with domain='.example.com' -- unchanged. Fix is to pass the original cookie's domain value into the set cookie statement that clears the session. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1824) Official documentation of replication algorithm?
[ https://issues.apache.org/jira/browse/COUCHDB-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686724#comment-13686724 ] Dave Cottlehuber commented on COUCHDB-1824: --- [~natevw] ditto, are you interested in picking this up? [~snej] we'd love your input on this too! > Official documentation of replication algorithm? > > > Key: COUCHDB-1824 > URL: https://issues.apache.org/jira/browse/COUCHDB-1824 > Project: CouchDB > Issue Type: Bug > Components: Documentation >Reporter: Nathan Vander Wilt > > Though it's in some ways an internal detail, it might be nice to provide a > canonical description of CouchDB's replication protocol (algorithm, really) > in the documentation. See links at: > http://wiki.apache.org/couchdb/Replication#Protocol_Documentation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1823) Automatic compaction not in official documentation
[ https://issues.apache.org/jira/browse/COUCHDB-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686723#comment-13686723 ] Dave Cottlehuber commented on COUCHDB-1823: --- [~natevw] are you keen to a crack at adding this yourself? https://couchdb.readthedocs.org/en/latest/contributing.html has some notes on this. > Automatic compaction not in official documentation > -- > > Key: COUCHDB-1823 > URL: https://issues.apache.org/jira/browse/COUCHDB-1823 > Project: CouchDB > Issue Type: Bug > Components: Documentation >Reporter: Nathan Vander Wilt >Assignee: Alexander Shorin > > I couldn't find the automatic compaction info at > https://wiki.apache.org/couchdb/Compaction in the official documentation. > Once this is migrated, it would be great to add more links to the official > versions atop the original wiki page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1819) Support style=main_only as an option on the source feed when replicating
[ https://issues.apache.org/jira/browse/COUCHDB-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686719#comment-13686719 ] Dave Cottlehuber commented on COUCHDB-1819: --- Thanks for logging a ticket on this Stephen. I can see why you might find this useful but this doesn't feel aligned to CouchDB for me. Functioning replication (without losing your data during conflict resolution :-) is one of our core features, and I can't see how this API change would play well with other Couch-like replication systems if they wish to stay compatible. Any more details on the use case? An alternative is to write your own replicator, see https://groups.google.com/forum/#!msg/nodejs/_v8G6yutMkg/HtgU596_C1QJ and https://github.com/mikeal/replicate for an example. The replicator is just a clever HTTP client, so you can do the same thing yourself. > Support style=main_only as an option on the source feed when replicating > > > Key: COUCHDB-1819 > URL: https://issues.apache.org/jira/browse/COUCHDB-1819 > Project: CouchDB > Issue Type: New Feature >Reporter: Stephen Bartell >Priority: Minor > > The goal is to not propagate conflicts and _deleted_conflicts. > This of course has the implication of blindly accepting couchdb's default > conflict resolution algorithm and not giving the user a chance fix conflicts. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COUCHDB-1819) Support style=main_only as an option on the source feed when replicating
[ https://issues.apache.org/jira/browse/COUCHDB-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Cottlehuber updated COUCHDB-1819: -- Priority: Minor (was: Major) > Support style=main_only as an option on the source feed when replicating > > > Key: COUCHDB-1819 > URL: https://issues.apache.org/jira/browse/COUCHDB-1819 > Project: CouchDB > Issue Type: New Feature >Reporter: Stephen Bartell >Priority: Minor > > The goal is to not propagate conflicts and _deleted_conflicts. > This of course has the implication of blindly accepting couchdb's default > conflict resolution algorithm and not giving the user a chance fix conflicts. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [RELEASE][REQUEST] Binaries for 1.3.1-rc.2
On 14 June 2013 15:30, Noah Slater wrote: > Cool. Thanks. I am on vacation until Tues. Is anyone else able to prepare > Win binaries? Done! https://dist.apache.org/repos/dist/dev/couchdb/binary/win/1.3.1/rc.2/ To test: - download - check sigs (like http://wiki.apache.org/couchdb/Test_procedure#Verifying_the_Candidate) - run the exe - launch Apache CouchDB from start menu - Run “Verify Installation” - Relax A+ Dave
svn commit: r2217 - /dev/couchdb/binary/win/1.3.1/rc.2/
Author: dch Date: Tue Jun 18 11:44:25 2013 New Revision: 2217 Log: Add 1.3.1-rc.2 win files Added: dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe (with props) dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.asc dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.build_pdbs-logs.tar.gz (with props) dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.md5 dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.sha dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R15B03-1.exe (with props) dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R15B03-1.exe.asc dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R15B03-1.exe.build_pdbs-logs.tar.gz (with props) dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R15B03-1.exe.md5 dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R15B03-1.exe.sha Added: dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe == Binary file - no diff available. Propchange: dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe -- svn:executable = * Propchange: dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe -- svn:mime-type = application/octet-stream Added: dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.asc == --- dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.asc (added) +++ dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.asc Tue Jun 18 11:44:25 2013 @@ -0,0 +1,18 @@ +-BEGIN PGP SIGNATURE- +Version: GnuPG/MacGPG2 v2.0.18 (Darwin) +Comment: GPGTools - http://gpgtools.org + +iQIcBAABAgAGBQJRwDN7AAoJEM2wwPkE9O6bu84P/2lsrsx/Te/sFVb5hw30WT5j +4DQU3/QXe2SwPNSh8CdM/MI0w8SOKR9pQWBC3Dqs08wVjA5oxHl9nqSI0E+E+H2y +XK/o7I5QThR11hKzGCIz4R6b3PO5E15pt2A9kttTh6ym26wCUo+aTlinuqRrGmX3 +TzJUtkmwyOE+ZqAHWkKzQFSs1Sxijd711RIPBSCzeXWy7t6D2JEpzuf3v4Vw7NAW +wVv1zKjlvlHsOtXQWr3l+4bRyXv8dHM9cmRnD3eQdOnRuer4LiNLNau10dyofIDs +j7JDQddO9WStqyH8qR7TXgqCLDZnTcpvFOnxqhW2Rd5sjRkuGZr/5Kr1e68a3vuD +PtjKqM/sFQRXtY662a9vnrdxLvVYUIbQ2d7bpAIZTZt5hMA4rfa35JvvpSOBOQg0 +YLhV69MNMwgq/6tN+bQqzSAqp7c9Dq65va/0aLjSY46PFtnAmGoec0u1snPsMEdU +S4SmSUkmh9u0WP0yKoOZft/duxCQV+q8FTGHT+2WZuoicsncREn+DaZZX3oOvUxr +qeQozpwG2gPAQE36FefHZ153RL1ylBPA1MrJPLiBpYVATlDfK4jC0AHHTwg7X6qf +sT8MaLwlw4uy7hT20amUkjnnCC9LpI1uxGDPEvozJjhwUdLerrVd7m6mccmIZ5k2 +i1ZpWkNcskAI8zLOZGJe +=JzdB +-END PGP SIGNATURE- Added: dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.build_pdbs-logs.tar.gz == Binary file - no diff available. Propchange: dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.build_pdbs-logs.tar.gz -- svn:mime-type = application/x-gzip Added: dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.md5 == --- dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.md5 (added) +++ dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.md5 Tue Jun 18 11:44:25 2013 @@ -0,0 +1 @@ +2a72599822d4afa5a9277b98b79e8ec7 *setup-couchdb-1.3.1_R14B04.exe Added: dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.sha == --- dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.sha (added) +++ dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R14B04.exe.sha Tue Jun 18 11:44:25 2013 @@ -0,0 +1 @@ +833414322e80cb2ab01dd070e763f7421791c205 *setup-couchdb-1.3.1_R14B04.exe Added: dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R15B03-1.exe == Binary file - no diff available. Propchange: dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R15B03-1.exe -- svn:executable = * Propchange: dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R15B03-1.exe -- svn:mime-type = application/octet-stream Added: dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R15B03-1.exe.asc == --- dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R15B03-1.exe.asc (added) +++ dev/couchdb/binary/win/1.3.1/rc.2/setup-couchdb-1.3.1_R15B03-1.exe.asc Tue Jun 18 11:44:25 2013 @@ -0,0 +1,18 @@ +-BEGIN PGP SIGNATURE- +Version:
svn commit: r2216 - in /dev/couchdb/binary/win/1.3.1: ./ rc.2/
Author: dch Date: Tue Jun 18 10:11:55 2013 New Revision: 2216 Log: Add 1.3.1-rc.2 win dir Added: dev/couchdb/binary/win/1.3.1/ dev/couchdb/binary/win/1.3.1/rc.2/
[REMINDER] IRC meeting - 2013-06-19 19:00 UTC
Hi all, We'll be having the usual meeting in #couchdb-meeting on irc.freenode.org at 19:00 UTC, Wednesday as usual. The meeting room: irc://irc.freenode.net/couchdb-meeting Or you can access the meeting via the web: http://webchat.freenode.net/?channels=#couchdb-meeting For your local timezone: http://arewemeetingyet.com/Wwed/19:00/CouchDB%20IRC%20Meeting If you have a specific topic we should talk about, reply here or bring it up on IRC. -- ,,,^..^,,,
