[Kde-pim] KDE 4.2 KPilot coming! (how to both be excited and have realistic expectations)

[Jason 'vanRijn' Kasper]

On Sat, Jan 24, 2009 at 6:01 AM, Gunter Ohrner <G.Ohrner at post.rwth-aachen.de
> wrote:

> Jason 'vanRijn' Kasper wrote:
> > I just wanted to get a note out to as wide a distribution list as
> > possible to spread some important news about the upcoming KDE 4.2
> > release and KPilot's (exciting!!) part in it. If you don't care about
>
> I just got Akonadi working and tested kpilot "Version 5.2.0-rc1 (KDE
> 4.2.0) Unter KDE 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1))" against my Palm
> Centro.
>
> The initial sync went fine (kOrganizer and the KDE addressbook were
> empty, and all records from my Centro got replicated.
>
> I tried editing calendar entries in kOrganizer, editing the subject of
> four appointments and changing categories. (I deleted category "Nicht
> abgel." ("Unfil.") within kOrganizer, as there also was a category "Nicht
> abgelegt" ("Unfiled") and changed the category of the four appointments
> from "Nicht abgel." to "Sport".)
>
> On the next sync, kpilot complained about an "invalid record mapping",
> did a full sync, and I ended up with both my old and my edited
> appointments on both systems:
>
> 11:46:24 [Abgleichmodul kpilot-conduit-calendar]
> 11:46:27 Invalid record mapping. Doing first sync.
> 11:46:27 Doing first sync. This may take a while.
> 11:46:29 HH data proxy: Beginn: 159. Ende: 164.5 Neu(e).
> 11:46:29 PC data proxy: Beginn: 160. Ende: 164.4 Neu(e).
>
> Then I deleted the old entries on kOrganizer again and did a third sync,
> which did not change anything, ie. the deletion was not replicated:
>
> 11:48:22 [Abgleichmodul kpilot-conduit-calendar]
> 11:48:25 HH data proxy: Beginn: 164. Ende: 164.Keine Änderungen
> durchgeführt.
> 11:48:25 PC data proxy: Beginn: 164. Ende: 164.Keine Änderungen
> durchgeführt.
>

Hi  Gunter!

One thing you should do to try to debug where things might be going wrong is
to run "akonadiconsole". Look in the browser view and see if things look
right. I've seen something like what you're describing before, and when I
looked in akonadiconsole, what I saw was that kpilot was doing the right
thing, and the data that was in akonadi didn't match the data that I saw in
korganizer.

I'll continue to test kpilot the next days and I'm already curious how
> well it will sync my contacts. So far my very first impression is rather
> good, kpilot did not lose any data so far and at least it did work at
> all, in contrast to kpilot from KDE 3.5.x with x >= 5.
>

Heh. Yeah, not losing data is a good thing!! =:) Duplicating data is not so
nice, but we try very hard to not lose data, so I think we're much better in
KDE 4.2 than we ever were before.

One other thing to note is that I've made a BUNCH of bug fixes even since
the rc1 release, so you may want to get the latest source code from svn (
http://kpilot.org/develop.php) if you run into any problems.

Thanks for testing Gunter! =:)

-- 
-[ Jason 'vanRijn' Kasper    //  http://movingparts.net ]-
-[ KDE PIM Developer         //  http://www.kde.org  ]-
-[ bash fun -> :(){ :|:&};:  //  Numbers 6:22-26 ]-
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/