On Sat, 2017-05-13 at 14:33 +0200, Vincent Lambert wrote:
Le 12/05/2017 à 09:13, Patrick Ohly a écrit :
> On Thu, 2017-05-11 at 15:45 +0200, Vincent wrote:
>> ----- Mail original -----
>>> De: "Patrick Ohly" <patrick.ohly(a)intel.com>
>>> À: "Vincent" <vincent.lambert9(a)free.fr>
>>> Cc: syncevolution(a)syncevolution.org
>>> Envoyé: Jeudi 11 Mai 2017 10:31:28
>>> Objet: Re: [SyncEvolution] "Comparison was impossible"
>>> Have you seen my latest reply in the mail thread? You didn't respond
>>> that, so perhaps it got lost. I'm attaching it again.
>> Yes I just anwsered you in the next message, here is the message:
> That mail didn't reach the list.
>> I first did a refresh-from-remote sync, but if I delete a
>> contact from my phone, a regular sync didn't delete it on the server. So
>> I tried with a complete reset of my config and database. I've deleted
>> all my contacts from the graphical app and did the slow sync. I have
>> always the same problem =(
> I lost track of what "the same problem" is. Are we still talking about
> the "Comparison was impossible" part or something else?
I understood that "Comparison was impossible" if often present in the
logs, so my main problem is I can't delete a contact on my phone, sync,
and get it deleted on the server, effectively after the
refresh-from-remote sync you recommanded.
>> [INFO] @default/contacts: started
>> [INFO] @default/contacts: sent 1
>> [INFO @owncloud] @owncloud/contacts: started
>> [INFO @owncloud] @owncloud/contacts: updating "Chloé"
>> [INFO @owncloud] @owncloud/contacts: received 1/1
>> [INFO] @default/contacts: normal sync done successfully
>> [INFO @owncloud] @owncloud/contacts: normal sync done successfully
> So "Chloé" was considered "modified" locally and thus updated on
> OwnCloud side. Directly after a "refresh from remote" that indeed
> shouldn't happen.
Yes, I think that is correct. I don't know why syncevolution behave like
So the "Chloe" contact was the one you deleted after the
I bet it wasn't actually deleted when you marked it as deleted on the
Let's verify that hypothesis.
Use "syncevolution --print-items @default contacts". It'll give you an
ID string for each contact. Then use "syncevolution --export - @default
contacts <id string of Chloe>" to dump the contact to your console.
Example (for my local setup, with "addressbook" instead of
$ syncevolution --print-items @default addressbook
pas-id-5406E78700000000: John Doe
$ syncevolution --export - @default addressbook pas-id-5406E78700000000
PRODID:-//Synthesis AG//NONSGML SyncML Engine V184.108.40.206//EN
Is there anything in your "Chloe" contact that might mark it as
If unsure, then dump it directly after the refresh-from-remote and again
after deleting it in the UI. If you can still dump it after deleting,
then it definitely wasn't deleted for real.
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.