Closed kwrobot closed 9 years ago
Comment #1 originally posted by kientzle on 2009-04-16T17:21:02.000Z:
What timezone are you in? <sigh>
Comment #2 originally posted by kientzle on 2009-04-16T17:21:44.000Z:
<empty>
Comment #3 originally posted by kientzle on 2009-04-16T17:44:10.000Z:
The archive has a timestamp of 1, which is indeed Dec 31, 1969 west of Greenwich but
Jan 1, 1970 east of Greenwich.
< -rw-r--r-- 1 1000 1000 0 Dec 31 1969 file
---
> -rw-r--r-- 1 1000 1000 0 Jan 1 1970 file
Changing the reference file will just break it in different timezones.
I've disabled this check in r1004 until I can come up with something more robust.
Comment #5 originally posted by kientzle on 2009-04-16T22:55:05.000Z:
Windows doesn't have /usr/bin/env.
Comment #6 originally posted by jsonn on 2009-04-16T22:59:58.000Z:
What about just using setenv()?
Comment #7 originally posted by kientzle on 2009-04-17T01:21:50.000Z:
"What about just using setenv()?"
That might work. Let's try that in trunk and see what happens. I'd rather not put
this change into 2.7 until we get thorough test coverage of it.
Comment #8 originally posted by kientzle on 2009-04-20T18:24:09.000Z:
After thinking about it some, I'm not enthusiastic about setenv(): the code to set
and then restore the TZ value is a little tedious, and I don't want to leave the
timezone set to UTC for every test, since we have seen bugs in the past that only
appeared in certain timezones.
Since we're testing a single line of output that has only two possible values,
I found it easier to just hardcode the two possibilities in the C source.
This should work on all platforms. Implemented in r1037.
Original issue 21 created by Google Code user
timothy.redaelli
on 2009-04-16T10:56:49.000Z:See attachment: libarchive-2.6.992a-test_option_t.patch