From: JS <js@direct.lv>
To: musl@lists.openwall.com
Subject: DST change issue for timezones in southern hemisphere
Date: Mon, 6 Mar 2017 12:44:53 +0200 [thread overview]
Message-ID: <34ea8f18-42d9-7817-7595-00435ac24b22@direct.lv> (raw)
Hi!
For some reason DST change in southern hemisphere occurs 1 hour late
when clock is turned backward and 1 hour early when clock is turned forward.
For example, timezone for spec for Brazil is:
BRT3BRST,M10.3.0/0,M2.3.0/0
Which means that DST change occurs at midnight.
Output of date for both DST changes:
~# date
Sun Feb 19 00:59:59 BRST 2017
~# date
Sun Feb 19 00:00:00 BRT 2017
~# date
Sat Oct 14 22:59:59 BRT 2017
~# date
Sun Oct 15 00:00:00 BRST 2017
I've tested the same code on same hardware but with uClibc library
instead of musl and it works fine.
next reply other threads:[~2017-03-06 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 10:44 JS [this message]
2017-03-15 19:01 ` Rich Felker
2017-03-16 0:41 ` Rich Felker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=34ea8f18-42d9-7817-7595-00435ac24b22@direct.lv \
--to=js@direct.lv \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).