On Sat, 2013-02-16 at 14:49 +0100, Christof Schulze wrote:
> This is from a sync from a phone using webdav as storage backend. I
> believe the 412 came from the webserver it is a valid http error code.
SyncML uses the same error codes. In this case, the 412 came from the
phone ("RECEIVED NON-OK STATUS 412" means "from the peer = phone").
> I use syncevolution to sync my phone to that storage and I also sync
> akonadi to that storage which is independent from syncevolution. i
> first synced all of the above then removed this contact from akonadi
> and I might have edited it on the phone at the same time. Then I
> triggered the sync that led to the 412. i war able to resolve the
> matter by manually creating a vcard with the expected name in the
> webdav, triggered a sync for a couple of times and the error was gone.
Without looking at the logs it's hard to tell how it resolved itself. My
bet would be that a slow sync was done eventually. That throws away the
(in this case probably broken) meta data and starts from scratch.
> Am I using syncevolution in an unintended way?
No, not at all. You are just using it like no-one has done before on a
regular basis (gateway between SyncML and WebDAV) and on low end
hardware, thus some of the issues (timeouts). The 412 looks like a bug
somewhere.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
