On 5/9/07, Malcolm Rowe <email@example.com> wrote:
> I'm not sure why there seems to be so much focus on client-server clock
> synchronisation in this thread, but anyway...
I think the assumption was that "Bogus date" had to be a date/time
issue. I personally didn't believe this to be the explanation, due to
similar mis-information in other svn error messages, but I went
through all the requisite steps to rule that out as the error source.
> That error is generated in just one place:
> libsvn_subr/svn_time_from_cstring(), where we attempt to convert a
> string to a time. From the looks of the messages above, I'm guessing
> that this is happening when re-reading the entries file to update it,
That's what I thought too, based on previous reports of the problems
with the vss2svn scripts. That's why, on a few occasions where this
error came up, I opened up the related .svn folders and looked at the
entries files, and some other cache files, as text. All the date/time
strings I could find matched the "2007-08-09T99:99:99.9999999Z"
pattern, so I gave up on that and ignored it. Having people more
familiar with the code than myself look at these files is a very good
idea, so the next time I will zip the .svn up and send it here.
> I don't think you mentioned this, but is there a way to generate the
> 'Bogus date' message _after_ the commit has failed?
The only other time we get that message is during cleanup, immediately
after the failed revision bump, on the folder where the commit
occurred. "In directory 'C:\Some\WC\Path'. Error processing command
'modify-entry' in 'C:\Some\WC\Path'. Bogus date." That is part of why
I was insisting this must be an error with the WC cache alone, and
previously suspected something was wrong with the 'entries' files.
Hopefully my next e-mail will contain a bad entries file to analyze...
It's hard to obtain one right away, because I don't have the same
problem on my own workstation, and the people who do have the problem
often update/resolve/revert to work around the issue before I have a
chance to copy their .svn folder.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed May 9 21:54:46 2007