On Tue, May 01, 2007 at 05:02:17PM -0700, Jared Hardy wrote:
> We recently changed subversion servers, and a week into using it,
> a random subset of my users are getting this error, most often upon
> committing newly added files:
> svn: Commit succeeded, but other errors follow:
> svn: Error bumping revisions post-commit (details follow):
> svn: Bogus date
I'm not sure why there seems to be so much focus on client-server clock
synchronisation in this thread, but anyway...
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,
though I don't see how that could be connected to your server change.
Unfortunately the error message doesn't differentiate between failing to
parse something that looks like a date ("2007-08-09T99:99:99.9999999Z")
and failing to parse something that doesn't ("foo"), nor does it
identify exactly which string it's trying to parse.
Unless I'm on completely the wrong track, something is causing a bogus
date to be written to the entries file or wc log files, so we should be
able to see that after the commit has failed. Could you zip (or tar) up
everything in a failing wc and make it available for analysis? You can
remove all of the versioned files and .svn-base files (inside
.svn/text-base) from the archive - we're just interested in the
metadata, not the file contents.
I don't think you mentioned this, but is there a way to generate the
'Bogus date' message _after_ the commit has failed? You mentioned
problems to do with getting the wc to the correct state, but it wasn't
clear whether these were just the normal problems anyone would have, or
specific to this problem.
Received on Wed May 9 17:04:13 2007
- application/pgp-signature attachment: stored