On Wed, 2015-05-27 at 17:00 +0200, Daniel CLEMENT wrote:
> Le mercredi 27 mai 2015 à 14:53 +0200, Patrick Ohly a écrit :
> > On Wed, 2015-05-27 at 14:04 +0200, Daniel CLEMENT wrote:
> > > [INFO] addressbook: deleting "Pioneer"
> > > [ERROR] addressbook: error code from SyncEvolution fatal error (local,
> > > status 10500): addressbook: deleting contact pas-id-5532AC2B00000000:
> > > FOREIGN KEY constraint failed
> > > [INFO] creating complete data backup of datastore calendar before sync
> > > (enabled with dumpData and needed for printChanges)
> > > *** calendar ***
> > > Comparison was impossible.
> > 
> > Looks like your local EDS database got corrupted during the distro
> > upgrade.
> 
> Certainly, even manual deletion of the above contact failed with
> "FOREIGN KEY constraint failed".
> 
> >  Can you report this to the distro and/or Evolution developers?
> 
> I'll do it ASAP.

Not necessary anymore, as Milan pointed out, it is a known (and fixed)
issue.

> Hmm... This did work for the address book, but alas not for the calendar
> and the memos. 
> 
> I tried and deleted ~/.local/share/evolution/memos/system/journal.ics
> (or /.local/share/evolution/calendar/system/calendar.ics) like I had
> done for /.local/share/evolution/addressbook/system/contacts.db.
> 
> Then e.g.
> syncevolution --sync refresh-from-remote memotoo memo
> gives me an error code 10508:
> 
> [1]daniel@e6330d ~ $ syncevolution --sync refresh-from-remote memotoo
> memo
> [INFO] addressbook: inactive
> [INFO] calendar: inactive
> [INFO] calendar+todo: inactive
> [INFO] todo: inactive
> [INFO] memo: starting first time sync from server (peer is server)
> [INFO] creating complete data backup of datastore memo before sync
> (enabled with dumpData and needed for printChanges)
> Local data changes to be applied during synchronization:
> *** memo ***
> no changes
> 
> [INFO] memo: first time sync done unsuccessfully
> [ERROR] memo: local, status 10508
> [ERROR] error code from Synthesis engine local, status 10508
> [INFO] creating complete data backup after sync (enabled with dumpData
> and needed for printChanges)
> 
> Synchronization failed,
> see 
> /home/daniel/.cache/syncevolution/memotoo-2015-05-27-16-57/syncevolution-log.html
>  for details.

What further details does that file have about the 508 error?

-- 
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]
https://lists.syncevolution.org/mailman/listinfo/syncevolution

Reply via email to