After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 769483 - re-occuring events date & time is incorrect after migration
re-occuring events date & time is incorrect after migration
Status: RESOLVED DUPLICATE of bug 766346
Product: evolution
Classification: Applications
Component: Calendar
3.20.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2016-08-03 18:26 UTC by KiaH
Modified: 2016-08-10 14:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
reoccurring event, has wrong time(-4 hours) extracted from the .tar.gz backup under .local/share/evolution/calendar/ (321 bytes, text/plain)
2016-08-03 18:26 UTC, KiaH
Details

Description KiaH 2016-08-03 18:26:13 UTC
Created attachment 332648 [details]
reoccurring event, has wrong time(-4 hours) extracted from the .tar.gz backup under .local/share/evolution/calendar/

Full bug description:
https://mail.gnome.org/archives/evolution-list/2016-July/msg00124.html
https://mail.gnome.org/archives/evolution-list/2016-August/msg00002.html
the closest bug that I think matches my problem is this:
https://bugzilla.gnome.org/show_bug.cgi?id=329420

On my "old" CentOS 7 I have these installed:
evolution-3.12.11-15.el7.x86_64
evolution-data-server-3.12.11-24.el7.x86_64
I create a .tar.gz backup file on this system, then go over to my new system Fedora Core24, which has:
evolution-3.20.4-1.fc24.x86_64
evolution-data-server-3.20.4-1.fc24.x86_64

I try to restore my calendar from the .tar.gz file but allmost all the reoccurring events show up on wrong date (a day before) or time(-4 hours). Non-reoccuring events have correct data & time.

Attached is an reoccurring event that I extracted from the .tar.gz backup* produced by the CentOS 7 (evolution-3.12.11-15.el7.x86_64), that shows up with -4 hours wrong time on my Fedora Core 24 (evolution-3.20.4-1.fc24.x86_64)
Comment 1 KiaH 2016-08-03 18:29:07 UTC
I have a couple of reoccuring events that show up with correct date and time.
Here is how one of them looks like: 
(text extracted from the .tar.gz backup under .local/share/evolution/calendar/ )

BEGIN:VEVENT
UID:20140714T165546Z-5678-500-1-1@localhost.localdomain
DTSTAMP:20140714T165546Z
DTSTART;TZID=/freeassociation.sourceforge.net/Tzfile/America/New_York:
 20140717T123000
DTEND;TZID=/freeassociation.sourceforge.net/Tzfile/America/New_York:
 20140717T130000
TRANSP:OPAQUE
SEQUENCE:9
SUMMARY:RI-er devel meeting
CLASS:PUBLIC
CREATED:20140829T135523Z
LAST-MODIFIED:20150729T144013Z
RRULE:FREQ=WEEKLY;INTERVAL=2
EXDATE;VALUE=DATE:20150730
EXDATE;VALUE=DATE:20150101
END:VEVENT
Comment 2 KiaH 2016-08-04 14:33:19 UTC
Clarifications regarding my attachment description:
In the attachment (the event with SUMMARY:SubmitWWorkday) the 
DTSTART:20160729T060000 is the correct time (6:00AM US EDT) but when I restore the backup file to my new system(FedoraCore24) then this event shows up at 2:00AM US EDT)
Comment 3 Milan Crha 2016-08-08 07:19:21 UTC
Thanks for a bug report. The difference between the attached event and the event pasted in the comment #1 is that the later has specified a time zone, while the former is defined as a floating time, which means "that hour/day in whatever timezone the user uses".

I think this is bug #766346.

*** This bug has been marked as a duplicate of bug 766346 ***
Comment 4 KiaH 2016-08-10 14:21:44 UTC
On my Fedora24 system, I just installed the latest 
evolution-data-server-3.20.5-1.fc24.x86_64
evolution-3.20.5-1.fc24.x86_64
and restored a tar.gz backup file from my CentOS7 system and now all my re-occuring events date & time show up correctly. 
Thank you for resolving this bug so quickly, appreciate it!
Comment 5 Milan Crha 2016-08-10 14:57:50 UTC
Nice, thanks for the confirmation.