[#13972] VTIMEZONE not generated correctly when exported to vCalendar
Summary VTIMEZONE not generated correctly when exported to vCalendar
Queue Horde Framework Packages
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester fzipi@fing.edu.uy
Created 2015-04-29 (1853 days ago)
Due
Updated 2015-11-09 (1659 days ago)
Assigned
Resolved 2015-11-09 (1659 days ago)
Milestone
Patch No

Comments
fzipi@fing.edu.uy 2015-04-29 20:31:36
VTIMEZONE is not generated correctly when exported to vCalendar.

I've had problems trying to import ics events from kronolith. The 
application trying to import uses the ical4j library, and apparently 
in this case exported data isn't conforming rfc 5545.

<begin code>
$tz = $GLOBALS['injector']->getInstance('Horde_Timezone');

$vTimezone = 
$tz->getZone('America/Montevideo')->toVtimezone()->exportvCalendar();

var_dump($vTimezone);
<end code>

The relevant part for this probles is near line 15:
...
BEGIN:STANDARD
TZOFFSETFROM:-0330
TZOFFSETTO:-0330
TZNAME:UY-T
END:STANDARD
BEGIN:STANDARD
TZOFFSETFROM:-0330
TZOFFSETTO:-0330
TZNAME:UYHST
END:STANDARD
...

This two entries must have DTSTART per rfc 5545.

fzipi@fing.edu.uy 2015-05-12 18:16:30
Bug reported in application is 
https://github.com/bitfireAT/davdroid/issues/489

Michael Rubinsky <mrubinsk@horde.org> 2015-05-18 21:40:38
I can reproduce the missing DTSTART properties when using the one 
specific timezone specified in the ticket (America/Montevideo). My 
guess is the tzdatabase is broken, but I'll have to take a closer look 
when I get time.

fzipi@fing.edu.uy 2015-10-13 19:36:58
This could happened by a broken timezone file indeed.

After updating tzdata package to tzdata-2015f this problem has disappeared.

You can close this one.