From owner-freebsd-bugs  Wed Apr 24 08:03:33 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA23398
          for bugs-outgoing; Wed, 24 Apr 1996 08:03:33 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA23389
          Wed, 24 Apr 1996 08:03:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id IAA11475; Wed, 24 Apr 1996 08:02:25 -0700 (PDT)
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
cc: jkh@freefall.freebsd.org (Jordan K. Hubbard), Mark.Olear@Colorado.EDU,
        freebsd-bugs@freefall.freebsd.org
Subject: Re: bin/1156 
In-reply-to: Your message of "Wed, 24 Apr 1996 08:39:45 +0200."
             <199604240639.IAA26158@uriah.heep.sax.de> 
Date: Wed, 24 Apr 1996 08:02:25 -0700
Message-ID: <11473.830358145@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Are you sure this was the same problem?  I doubt:
> 
> j@uriah 68% env TZ=America/Denver date
> Wed Apr 24 00:37:04 EDT 1996
> 
> I think Denver is some hours west of EDT, isn't it?

Actually, it seems that I did indeed misread his problem report (I
thought it was the tzsetup bug where it would choose the wrong file
for you, even though it *said* you were getting Denver) and the
timezone file for Denver was, in fact, wrong.

However:

root@time-> env TZ=America/Denver date
Wed Apr 24 08:59:25 EDT 1996
root@time-> cd /usr/src/share/zoneinfo/
root@time-> make all install
umask 022; cd /a/src-current/share/zoneinfo;  zic -d /usr/share/zoneinfo -p America/New_York   -y /a/src-current/share/zoneinfo/obj/yearistype africa antarctica asia australasia etcetera europe  factory northamerica southamerica systemv
chown -R bin.bin /usr/share/zoneinfo/*
root@time-> env TZ=America/Denver date
Wed Apr 24 08:59:54 MDT 1996

It looks like it was fixed anyway in our sources sometime
post-2.2-snap and so I don't have to reopen this bug report. :-)

					Jordan