Re: [bugs] problem with caldav syncing

> Le 8 déc. 2016 à 21:51, Lukas Fleischer <lfleischer@xxxxxxxxxxxx> a écrit :
> 
> On Thu, 08 Dec 2016 at 21:18:46, Guillaume Laurès wrote:
>> Not a big deal (the executable do compile fine) but just for you to know : I got an error on "make" :
>> (...)
>> Making all in doc
>> make[2] : on entre dans le répertoire « /home/meme/calcurse/doc »
>> make[2]: ***  Aucune règle pour fabriquer la cible « calcurse.1 », nécessaire pour « all-am ». Arrêt.
>> make[2] : on quitte le répertoire « /home/meme/calcurse/doc »
>> make[1]: *** [all-recursive] Erreur 1
>> make[1] : on quitte le répertoire « /home/meme/calcurse »
>> make: *** [all] Erreur 2
>> 
>> Got the same error earlier on 4.2.1 tarball btw.
> 
> This probably happens because you don't have a2x/AsciiDoc installed
> which is needed to generate the man page and the documentation.

True, "yum install asciidoc" fixed it !.

> 
>> 
>> Now, you will find attached the --debug traces for :
>> [...]
>> New sync database entry: /dav/meme-test@xxxxxxxxxxxxxxx/Calendar/b68447d9-ac52-4868-b312-3889f753631f.1479361338377.ics 18-18 11/18/2016 @ 20:10 -> 11/18/2016 @ 20:30|Guillaume
> 
> Oh. Turns out that for regular appointments, we were storing full
> serialized items instead of hashes in the sync database.
> 
> Should be fixed in master. Thanks for reporting!
> 

True, it works like a charm now :
calcurse-caldav --init=keep-remote
Connecting to mail.lauresfamily.fr...
Removing all local calcurse objects...
Importing new object 43-43.
Importing new object 42-42.
Importing new object 40-40.
Importing new object 41-41.
Importing new object 44-44.
Importing new object 45-45.
Saving synchronization database to /home/meme/.calcurse/caldav/sync.db...
6 items imported, 0 items removed locally.
0 items exported, 0 items removed from the server.

> Regards,
> Lukas
> 
> P.S.: Looks like you forgot to strip the authorization tokens from the
> debug output -- they can be used to recover your password. Probably not

True, how do you do that, for next time...?

> an issue since the credentials you used seem to be test credentials.
> Maybe we should do something about it and remove secret data from the
> debug automatically, though. I have seen several people publishing their
> user name and password unintentionally by copy-pasting debug logs...
> 

Thanks for having fixed it so quickly. Still doing a backup before each sync though for a few days...

Guillaume

Links