Closed Bug 455752 Opened 16 years ago Closed 16 years ago

Update internal timezone database to version 2008i

Categories

(Calendar :: Internal Components, defect)

Sunbird 0.9
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ssitter, Assigned: dbo)

References

()

Details

Attachments

(1 file, 1 obsolete file)

Sunbird 0.9 ships with timezone database version 2008d.

The latest released timezone database is version 2008f.
ftp://elsie.nci.nih.gov/pub/tzdata2008f.tar.gz

The internal database should be updated to reflect the changes.
IMO a good chance to push out the first calendar-timezones.xpi to AMO :)
For Sunbird this might work.

What about Lightning? As I understand this needs to wait until 1.0 or there needs to be e.g. a 0.9.1 release (0.9 + timezone updates).
Users can install calendar-timezones.xpi in Thunderbird and lightning should stick to it. This is not an auto-magic update like we (hopefully, nobody tested yet) get in Sunbird, but it ought to be possible to update timezones without a new release.
Depends on: 435474
Version 2008g is available:
    ftp://elsie.nci.nih.gov/pub/tzcode2008g.tar.gz
    ftp://elsie.nci.nih.gov/pub/tzdata2008g.tar.gz
Summary: Update internal timezone database to version 2008f → Update internal timezone database to version 2008g
Flags: blocking-calendar1.0+
Blocks: 459184
Blocks: 461201
Summary: Update internal timezone database to version 2008g → Update internal timezone database to version 2008i
Attached patch update to tzdata2008i (obsolete) — — Splinter Review
BTW: I needed to patch vzic-1.3 (vzic-parse.c) to allow years > 2037.

Update log:

Changes needed for /Volumes/data/moz_cc/src/calendar/locales/../timezones/../../calendar/locales/en-US/chrome/calendar/timezones.properties:
---
add    pref.timezone.America.Argentina.Salta=America/Argentina/Salta
---


timezone has been updated: America/Argentina/Buenos_Aires
timezone has been updated: America/Argentina/Catamarca
timezone has been updated: America/Argentina/Cordoba
timezone has been updated: America/Argentina/Jujuy
timezone has been updated: America/Argentina/La_Rioja
timezone has been updated: America/Argentina/Mendoza
timezone has been updated: America/Argentina/Rio_Gallegos
timezone has been updated: America/Argentina/San_Juan
timezone has been updated: America/Argentina/Tucuman
timezone has been updated: America/Argentina/Ushuaia
timezone has been updated: America/Campo_Grande
timezone has been updated: America/Cuiaba
timezone has been updated: America/Sao_Paulo
timezone has been updated: Asia/Damascus
timezone has been updated: Asia/Gaza
timezone has been updated: Indian/Mauritius
timezone has been updated: Pacific/Niue
timezone: Pacific/Wallis    [t]ake over as is or use [a]lias? t


Changes needed for /Volumes/data/moz_cc/src/calendar/locales/../timezones/../../calendar/locales/en-US/chrome/calendar/timezones.properties:
---
---



DONE.
Assignee: nobody → daniel.boelzle
Attachment #345265 - Flags: review?(ssitter)
Comment on attachment 345265 [details] [diff] [review]
update to tzdata2008i

I can't review that patch. |hg import| throws an exception and |patch| doesn't consider the binary changes when using a clean source tree.
Maybe you are using a different hg version? I use 1.0.2.

$ wget -O tz-patch "https://bugzilla.mozilla.org/attachment.cgi?id=345265"
$ hg import --force --no-commit tz-patch

works for me on a fresh tree.
Status: NEW → ASSIGNED
Attached patch update to tzdata2008i — — Splinter Review
fixed version
Attachment #345265 - Attachment is obsolete: true
Attachment #346687 - Flags: review?(mschroeder)
Attachment #345265 - Flags: review?(ssitter)
Attachment #346687 - Flags: review?(mschroeder) → review+
Comment on attachment 346687 [details] [diff] [review]
update to tzdata2008i

Works fine, but more testing after checkin would be great; r=mschroeder
Pushed to comm-central <http://hg.mozilla.org/comm-central/rev/c0114ba61e80>

-> FIXED
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0
No longer blocks: 459184
These bugs are likely targeted at Lightning 1.0b1, not Lightning 1.0. If this change was done in error, please adjust the target milestone to its correct value. To filter on this bugspam, you can use "lightning-10-target-move".
Target Milestone: 1.0 → 1.0b1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: