From dev-return-24373-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Wed Dec 5 07:35:01 2012 Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4AC33DFC5 for ; Wed, 5 Dec 2012 07:35:01 +0000 (UTC) Received: (qmail 80408 invoked by uid 500); 5 Dec 2012 07:35:00 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 80249 invoked by uid 500); 5 Dec 2012 07:34:59 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 79619 invoked by uid 99); 5 Dec 2012 07:34:58 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2012 07:34:58 +0000 Date: Wed, 5 Dec 2012 07:34:58 +0000 (UTC) From: "Fedor Indutny (JIRA)" To: dev@couchdb.apache.org Message-ID: <1612910333.62515.1354692898241.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (COUCHDB-1623) Replication of user database and conflicts MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Fedor Indutny created COUCHDB-1623: -------------------------------------- Summary: Replication of user database and conflicts Key: COUCHDB-1623 URL: https://issues.apache.org/jira/browse/COUCHDB-1623 Project: CouchDB Issue Type: Bug Components: Database Core, Replication Reporter: Fedor Indutny Heya, I'm trying to setup a private couchdb clone of npm repository: http://isaacs.iriscouch.com/registry And apparently I'll need to make authorization work, I've replicated http://isaacs.iriscouch.com/public_users database and set is as authentication_db. But authorization doesn't seem to be working, because couchdb's database contains a lot of conflicts for almost every user... So, basically how could one resolve it? And why documents with conflicts were replicated at all? Also, after removing conflicting revisions, authentication doesn't seem to be working (while it does in upstream database). Cheers, Fedor. -- 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