[darcs-users] strange timestamp in test directory

[David Roundy]

On Tue, Jun 22, 2004 at 11:58:08AM +1000, Peter Maxwell wrote:
> Patched files in the temporary test directory created by "darcs apply 
> the time that isn't a problem (eg: bash just says they date from 1 Jan 
> 1970), but if the file is a Python module it becomes a critical error 
> (see python bug #976608 at sourceforge).  This makes my tests fail.
> 
> Clues:
>  1) "darcs apply --test" has this problem, but "darcs apply --no-test 
> && darcs check --test" doesn't.
>  2) It didn't do that a week ago when I was using (I think) darcs 
> 0.9.19.
>  3) It occurs with both current darcs and darcs 0.9.20 on debian linux.
>  4) It doesn't occur on a mac with darcs 0.9.21.
> 
> The script I've been using to test for this behaviour is appended.  
> Just look for "5 Jan  1  1970 afile.txt" in the output.

Thanks for identifying this bug! I've actually been seeing this error, but
only on one computer, and thought that it was something in the
configuration of that computer that was messed up.  It turns out to be a
really stupid mistake of mine, and easily located and fixed.
-- 
David Roundy
http://www.abridgegame.org