In article <29170.113...@jinx.noi.kre.to>,
Robert Elz wrote:
>Date:Wed, 17 Apr 2019 14:24:40 +0800 (PST)
>From:Paul Goyette
>Message-ID:
>
> | I'd guess that a recent import of the latest tzcode has gone awry.
>
>I have seen this too, and when I get a few
In article <20190417061128.ga1...@primenet.com.au>,
Geoff Wing wrote:
>Hi,
>running /sbin/dmesg and /bin/date I am seeing a timezone name of "LMT" instead
>of my normal "AEST"
>
>Copying "date" and my zoneinfo file from a working computer, I still see bad
>info.
>
>From -current (compiled myself
Date:Wed, 17 Apr 2019 14:24:40 +0800 (PST)
From:Paul Goyette
Message-ID:
| I'd guess that a recent import of the latest tzcode has gone awry.
I have seen this too, and when I get a few minutes (if Christos has
not fixed it first) I will work out what is going
On my 8.99/35 system from last month I get
$ TZ=Australia/Melbourne date; TZ=NZ date
Wed Apr 17 16:21:31 AEST 2019
Wed Apr 17 18:21:31 NZST 2019
$
On an 8.99.37 within qemu (built only a couple days ago), I get
# TZ=Australia/Melbourne date; TZ=NZ date
Wed Apr
Hi,
running /sbin/dmesg and /bin/date I am seeing a timezone name of "LMT" instead
of my normal "AEST"
Copying "date" and my zoneinfo file from a working computer, I still see bad
info.
>From -current (compiled myself and from nyftp snapshot):
% TZ=Australia/Melbourne date; TZ=NZ date
Wed Apr 17
