[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: timezone data packaged separately and in volatile?



Am 2006-02-07 14:40:52, schrieb Ian Jackson:

>  2. The package fixes a critical bug which can lead into data loss,
>  data corruption, or an overly broken system, or the package is broken
>  or not usable (anymore).
> 
> That seems to be true in this case.  I think a system which gets the
> clock wrong in this way is `overly broken'.

And if you have scheduler which take critical operations (erasing
of files or or something similar) it would be critical.

> There doesn't seem to be anything in those rules which allows for an
> analysis of the risk, so that it can be compared to the benefit.
> (Perhaps that's implicit, although it's not stated.)  A timezone
> update, carefully built against the right dependencies, could be
> diffed (that is, the .deb could be diffed) against the old version and
> carefully tested, which would provide us with confidence that the new
> package is right to install.

I have an international database where I need correct timezones.
Currently I have a server side script for Australian $USERS.
 
> Ian.

Greetings
    Michelle Konzack
    Systemadministrator
    Tamay Dogan Network
    Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack   Apt. 917                  ICQ #328449886
                   50, rue de Soultz         MSM LinuxMichi
0033/3/88452356    67100 Strasbourg/France   IRC #Debian (irc.icq.com)



Reply to: