yes, you should be able to delete it (I can, locally). Running out of ideas but could you try double quotes around the rev? i.e, ?rev="131-57b4da8d3163468cb0bbf4fd30c87832"
B. On 2 March 2012 14:32, Jan Lehnardt <[email protected]> wrote: > Was the replication doc created in a 1.1.x CouchDB? > > Cheers > Jan > -- > > On Mar 2, 2012, at 14:58 , Stefan Kögl wrote: > >> On Fri, Mar 2, 2012 at 2:54 PM, Robert Newson <[email protected]> wrote: >>> could you redo the DELETE or PUT with '-sv' so we can see what's >>> really being sent? Perhaps there's a weird shell thing happening >>> causing the rev to be sent incorrectly. >> >> >> $ curl -sv -X DELETE >> "http://stefan:*********@127.0.0.1:5984/_replicator/mygpo?rev=131-57b4da8d3163468cb0bbf4fd30c87832"; >> * About to connect() to 127.0.0.1 port 5984 (#0) >> * Trying 127.0.0.1... connected >> * Connected to 127.0.0.1 (127.0.0.1) port 5984 (#0) >> * Server auth using Basic with user 'stefan' >>> DELETE /_replicator/mygpo?rev=131-57b4da8d3163468cb0bbf4fd30c87832 HTTP/1.1 >>> Authorization: Basic ********************** >>> User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k >>> zlib/1.2.3.3 libidn/1.15 >>> Host: 127.0.0.1:5984 >>> Accept: */* >>> >> < HTTP/1.1 409 Conflict >> < Server: CouchDB/1.2.0 (Erlang OTP/R14B04) >> < Date: Fri, 02 Mar 2012 13:57:01 GMT >> < Content-Type: text/plain; charset=utf-8 >> < Content-Length: 58 >> < Cache-Control: must-revalidate >> < >> {"error":"conflict","reason":"Document update conflict."} >> * Connection #0 to host 127.0.0.1 left intact >> * Closing connection #0 >> >> I verified the rev before and after the DELETE to make sure it hasn't >> changed in between. >> >> >>> On 2 March 2012 13:51, Robert Newson <[email protected]> wrote: >>>> tbh you should be getting this error: 'Only the replicator can edit >>>> replication documents that are in the triggered state'. I do. >> >> Shouldn't I be able to DELETE the replication document? >> >> >> -- Stefan >
