Here is a brief description of the problem: "The problem is that timezone updates happen frequently. Therefore timezones were split out of the glibc package so they can be updated separately via volatile.debian.org and point release updates. Every package that ships it's own timezone information needs extra care (which usually means it gets outdated rather quickly). So the goal is to use glibc's timezones from the tzdata package (which e.g. python-dateutil uses) everywhere." I am not sure how best to handle this problem. The best obvious solution would be to configure calendarserver to use this timezone database. But, looking at the code for pycalendar, I really doubt if calendarserver will be able to parse libc zoneinfo files. The only other option is to generate the ics files from the zoneinfo database. Any suggestion on how to handle this problem would be appreciated. Regards, Rahul.