#645102 syncevolution: time of recurring events changes

Package:
syncevolution
Source:
syncevolution
Description:
Sync personal information data via SyncML/CalDAV/CardDAV (CLI)
Submitter:
Michael Below
Date:
2021-11-29 06:00:05 UTC
Severity:
normal
#645102#5
Date:
2011-10-12 14:06:20 UTC
From:
To:
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

#645102#10
Date:
2011-10-12 14:35:46 UTC
From:
To:
Good that you finally found a solution before you replace the E71 ;-)

Are you sure that this only happens if there is such an overlap with an
existing event? In other words, if you remove that one-time event and
then create the recurring one, does the recurring event still not
display right?

Time zones can cause such issues in particular around the transitions
between standard and daylight saving time. But I have never heard of
such an interaction between events. This month we are also safely back
to standard, non-daylight saving time.

#645102#15
Date:
2011-10-12 14:35:46 UTC
From:
To:
Good that you finally found a solution before you replace the E71 ;-)

Are you sure that this only happens if there is such an overlap with an
existing event? In other words, if you remove that one-time event and
then create the recurring one, does the recurring event still not
display right?

Time zones can cause such issues in particular around the transitions
between standard and daylight saving time. But I have never heard of
such an interaction between events. This month we are also safely back
to standard, non-daylight saving time.

#645102#20
Date:
2019-08-25 00:50:57 UTC
From:
To:
Dear submitter,

as the package syncevolution has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/935239

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

#645102#33
Date:
2021-11-29 05:57:42 UTC
From:
To:
This bug has likely been fixed in the last decade, please check
syncevolution version 2.0.0-3 from Debian testing/bookworm or later.
If you still have the same issue, please report it upstream and let us
know the URL of the new upstream issue.

https://syncevolution.org/support