Forum OpenACS Development: What's the best approach to update timezone rules?

I've found some problems with timezone rules using America/Montevideo.
I've found in table timezone rules that it is not updated ( as seen doing:select * from timezone_rules where tz_id = 130)

What's the best approach to update timezon rules? (I've seen https://openacs.org/forums/message-view?message_id=135708 )

Is there some mecanism to keep timezones updated?

Thanks
Cesáreo

Sorry about the poor explanation. No, I mean add a rule to a specific timezone so it works properly.

As I've seen I could do a "insert rule in timezone_rules" for a specific timezone (with a specific tz_id) but I'm wondering it there is a way more "automatic".

My problem is with Timezone 'America/Montevideo' (in my installation tz_id = 130) . I think timezone rules are not properlly installed (I think DST rule).

I've checked openacs/packages/ref-timezones/sql/common/timezone-rules.dat
and it seems to be that rules are right but it seems to be an openacs update. I think (but I'm not sure) that upgrade-timezones.ctl didn't run) and before do that I ask

This is what I see in my database:

------ America/Montevideo is tz_id 130 ----
select * from timezones where tz ~ 'Mont';

 tz_id |             tz              | gmt_offset
-------+-----------------------------+------------
   113 | America/Kentucky/Monticello | -050000
   129 | America/Monterrey           | -060000
   130 | America/Montevideo          | -030000
   131 | America/Montreal            | -050000
   132 | America/Montserrat          | -040000
------ Timezone Rule (showing 4 records) -----
select * from timezone_rules where tz_id = 130 order by local_start desc limit 4;

 tz_id | abbrev |       utc_start        |        utc_end         |      local_start       |       local_end        | gmt_offset | isdst_p
-------+--------+------------------------+------------------------+------------------------+------------------------+------------+---------
   130 | UYT    | 1993-02-28 04:00:00-03 | 2038-01-18 06:14:07-02 | 1993-02-27 14:00:00-02 | 2038-01-18 15:14:07-02 | -10800     | f
   130 | UYST   | 1992-10-18 05:00:00-02 | 1993-02-28 03:59:59-03 | 1992-10-18 03:00:00-02 | 1993-02-27 14:59:59-02 | -7200      | t
   130 | UYT    | 1992-03-01 04:00:00-03 | 1992-10-18 04:59:59-02 | 1992-02-29 14:00:00-02 | 1992-10-17 12:59:59-03 | -10800     | f
   130 | UYST   | 1991-10-27 06:00:00-02 | 1992-03-01 03:59:59-03 | 1991-10-27 03:00:00-02 | 1992-02-29 14:59:59-02 | -7200      | t

Thanks!
Cesáreo

Yeah, it seems to be an upgrade problem. I'll load into database openacs/packages/ref-timezones/sql/postgresql/upgrade/upgrade-timezones.ctl

So the best approach seems to be:
1. Check rules in packages/ref-timezones/sql/common/timezones-rules.dat
2. Upgrade (vía upgrade-timezones.ctl or via apm-callback-procs.tcl)

Thanks !
Cesáreo