The document is updated periodically, I expect you just had the wrong _rev? On 2 March 2012 12:25, Stefan Kögl wrote: > Hi, > > Again something I noticed during my 1.2.x experiments: It seems I > can't update or remove a document from the _replicator database, which > I use for pull-replication into my 1.2.x instance. > > # get current _rev > $ curl http://127.0.0.1:5984/_replicator/mygpo > {"_id":"mygpo","_rev":"131-57b4da8d3163468cb0bbf4fd30c87832","source":"************************","target":"http://127.0.0.1:5984/mygpo","create_target":false,"continuous":true,"user_ctx":{"name":"stefan","roles":["admin"]},"owner":"stefan","_replication_state":"triggered","_replication_state_time":"2012-03-02T02:56:12+00:00","_replication_id":"f9fc5457b278d3cdb1ba2f1881253b04"} > > # try to delete > $ curl -X DELETE > "http://127.0.0.1:5984/_replicator/mygpo?_rev=131-57b4da8d3163468cb0bbf4fd30c87832" > {"error":"conflict","reason":"Document update conflict."} > > # try to update > $ cat replication.json > { >    "_id": "mygpo", >    "_rev": "131-57b4da8d3163468cb0bbf4fd30c87832", >    "_deleted": true, >    "source": "************************", >    "target": "http://stefan:********@127.0.0.1:5984/mygpo", >    "create_target": false, >    "continuous": true, >    "user_ctx": { >        "name": "stefan", >        "roles": ["admin"] >    } > } > > $ curl -X PUT "http://127.0.0.1:5984/_replicator/mygpo" -d @replication.json > {"error":"conflict","reason":"Document update conflict."} > > # check if rev has been updated in the meantime (but it hasn't) > $ curl http://127.0.0.1:5984/_replicator/mygpo > {"_id":"mygpo","_rev":"131-57b4da8d3163468cb0bbf4fd30c87832","source":"************************","target":"http://127.0.0.1:5984/mygpo","create_target":false,"continuous":true,"user_ctx":{"name":"stefan","roles":["admin"]},"owner":"stefan","_replication_state":"triggered","_replication_state_time":"2012-03-02T02:56:12+00:00","_replication_id":"f9fc5457b278d3cdb1ba2f1881253b04"} > > > Did I just spot a bug or am I simply doing something wrong? I tried to > find any clues in [1], which seems to be a semi-official > documentation, but without luck. > > > -- Stefan > > > [1] https://gist.github.com/832610