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

chroots of some archs fail to take DST into account?



Hi,

mercurial's testsuite has a test called "test-parse-date.t" that
checks that mercurial works across timezones.  The test passes in
chroots of some archs[0] but fails in others (e.g.[1] or [2]).

To reproduce the behaviour you don't need to run mercurial's
testsuite.  You don't even need python, you just need date(1).  When
your TZ is set to "PST+8PDT", Daylight Saving Time dates are reported
by date(1) in PDT:

$ TZ=PST+8PDT date --date=@1152995400
Sat Jul 15 13:30:00 PDT 2006

Now if you go to the arm64 porter box (asachi) and get into a chroot
you get the correct output:

vicho@asachi:~$ schroot -c sid -- env TZ=PST+8PDT date --date=@1152995400
I: 00check: Untarring chroot environment.  This might take a minute or two.
I: 99porterbox-extra-sources: o To install build dependencies run
I: 99porterbox-extra-sources:   dd-schroot-cmd -c sid_arm64-dchroot-4c6d35a0-ebb7-4660-9aa1-55827473177b apt-get update
I: 99porterbox-extra-sources:   followed by build-dep/install as appropriate in the host system.
I: 99porterbox-extra-sources: o If you started this session with schroot -b, please do not forget to run
I: 99porterbox-extra-sources:   schroot --end-session -c sid_arm64-dchroot-4c6d35a0-ebb7-4660-9aa1-55827473177b
I: 99porterbox-extra-sources:   when you no longer need this environment.
Sat Jul 15 13:30:00 PDT 2006
vicho@asachi:~$

In the armhf porterbox I get PDT (correct) in the machine itself, but
PST (wrong) in the chroot:

vicho@harris:~$ TZ=PST+8PDT date --date=@1152995400
Sat Jul 15 13:30:00 PDT 2006
vicho@harris:~$ schroot -c sid -- env TZ=PST+8PDT date --date=@1152995400
I: 00check: Untarring chroot environment.  This might take a minute or two.
I: 99porterbox-extra-sources: o To install build dependencies run
I: 99porterbox-extra-sources:   dd-schroot-cmd -c sid_armhf-dchroot-cc11a689-9117-420a-9009-d3cb074b87d6 apt-get update
I: 99porterbox-extra-sources:   followed by build-dep/install as appropriate in the host system.
I: 99porterbox-extra-sources: o If you started this session with schroot -b, please do not forget to run
I: 99porterbox-extra-sources:   schroot --end-session -c sid_armhf-dchroot-cc11a689-9117-420a-9009-d3cb074b87d6
I: 99porterbox-extra-sources:   when you no longer need this environment.
Sat Jul 15 12:30:00 PST 2006

This makes the test fail.  As far as I understand it, this is wrong,
the chroot's date output should have been in PDT.  Is this correct?
Are chroots of some architectures misconfigured and they fail to take
into account daylight information properly?

Cheers,
Javi

[0] https://buildd.debian.org/status/fetch.php?pkg=mercurial&arch=arm64&ver=3.7.1-1&stamp=1455235321
[1] https://buildd.debian.org/status/fetch.php?pkg=mercurial&arch=armhf&ver=3.7.1-1&stamp=1455245028
[2] https://buildd.debian.org/status/fetch.php?pkg=mercurial&arch=mips&ver=3.7.1-1&stamp=1455340824

Attachment: signature.asc
Description: PGP signature


Reply to: