2038 is when Unix systems run out of time. 1/1/1970 + 2^31 seconds =
sometime in 2038.
Sly
Rob Oxspring <roxspring@imapmail.org> wrote:
> Before anyone gets too excited I've not been able to reproduce the
> bug but more on that later...
>
> I was happily building a svn repo from lots of backups of various
> docs when subversion fell over taking the repo with it. The working
> copy was inconsistent and svnadmin could no longer dump the repo. On
> closer inspection the files that caused the problem were all dated in
> 2099 (I assume that my system was screwed up in 1999 for a while).
> The nasty part is that "svn add" dealt with the files happily and it
> was only at the "svn ci" stage that the problem occurred so the repo
> was taken down in addition to the wc.
>
> I didn't take note of the full details of the errors / messages since
> I figured I'd build a reproduction script to send instead.
> Unfortunately my copy of touch (from
> http://unxutils.sourceforge.net/) wouldn't let me create files dated
> later than 2038 which were added to a test repo without problem. I'm
> guessing the problem is either while parsing or its an overflow issue
> with the date.
>
> So, can others reproduce this? If so then can I request a slightly
> more graceful failure at minimum so that time travelling fools such
> as myself don't get burnt so badly (okay so in my case it was easy to
> rebuild the repo but for others it might not be)
>
> Thanks,
>
> Rob
>
> Win XP, Svn 0.29
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 17 01:29:10 2003