Package: syncevolution Version: 1.1.99.5a-2+b1 Severity: normal Dear Maintainer,
today I finally managed to sync my Nokia E71 to Evolution 3.0.3. This is great! I have been trying to do this on and off for years... But there is a slight problem: when I create a recurring event in Evolution, and it is parallel to another event already known to the E71, the time of the new event is changed. E.g. I have an existing event on the 5th at 18:00 and add a recurring event on 1, 3, 5, 7 and 9 at 19:30. Now the E71 shows the new event at 19:30 on the 1st and 3rd, and at 18:30 on the 5th and 7th. The last event is correct at 19:30 again. Maybe this is somehow a matter of time zones? I'm in Berlin, GMT +2. Thanks for your effort... Michael Below -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable'), (10, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages syncevolution depends on: ii libc6 2.13-21 ii libdbus-1-3 1.4.16-1 ii libgcc1 1:4.6.1-4 ii libglib2.0-0 2.28.6-1 ii libgnome-keyring0 3.2.0-2 ii libstdc++6 4.6.1-4 ii libsyncevolution0 1.1.99.5a-2+b1 ii syncevolution-common 1.1.99.5a-2 ii syncevolution-libs 1.1.99.5a-2+b1 Versions of packages syncevolution recommends: ii bluez 4.96-1 ii evolution-data-server 3.0.3-1 syncevolution suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
