Re: [gentoo-amd64] Problem with latest timezone update?

[nicolas@litchinko.fr (Nicolas Litchinko)]

Hi,

On Wed, Jan 16, 2008 at 05:37:21PM -0800, Mark Knecht wrote:
> On Jan 16, 2008 4:56 PM, Drake Donahue <donahue95@comcast.net> wrote:
> > Thus etc-update and/or dispatch-conf can't change localtime; but can change
> > whether localtime runs or not.
> 
> Humm...seems like what you say is true but doesn't explain how emerge
> -DuN system changed the file. It was clearly changed since I could
> look inside with vi and compare to the Los_Angeles file and see that
> they were clearly different...

There's a variable in /etc/conf.d/clock that controls whether or not
/etc/localtime should be updated when a new version of
sys-libs/timezone-data is merged: TIMEZONE. If this variable is set, the
specified timezone data file is copied over /etc/localtime.

as you can read in /etc/conf.d/clock:
# Select the proper timezone.  For valid values, peek inside of the
# /usr/share/zoneinfo/ directory.  For example, some common values are
# "America/New_York" or "EST5EDT" or "Europe/Berlin".  If you want to
# manage /etc/localtime yourself, set this to "".

If TIMEZONE is not set, /etc/localtime is not updated by
sys-libs/timezone-data. However, if TIMEZONE is set to an invalid value,
then /etc/localtime is overwritten by the "Factory" timezone data file. 

etc-update has probably changed the value of this variable after a
baselayout update. Then a timezone-data update used the wrong value to
update /etc/localtime. In your, case, the value of TIMEZONE should be
TIMEZONE="America/Los_Angeles".

-- 
Nicolas Litchinko
BOFH excuse #348:
We're on Token Ring, and it looks like the token got loose.
-- 
gentoo-amd64@lists.gentoo.org mailing list