> 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
On 5/2/07, John Peacock <email@example.com> wrote:
> Are you sure that the workstations *and* the server have the correct
> time (and the appropriate DST fix)?
I have already established that this is not a time issue. All the
clients involved are synced to the server via a login script that runs
this command every day: "net time \\subversion-server /set /yes". They
have also all had this command run at some point: "net time
/setsntp:"subversion-server backup-server time.nist.gov
time.windows.com". I'm pretty sure they all have the DST fix, though
that doesn't matter if the clients are synced to the server, because
if they're wrong, they're all wrong in the same way, right? Also, the
new and old servers have been set to the exact same time. Besides,
doesn't svn use GMT?
Can anyone tell me why this only affects the "bumping revisions"
after commit? No other command has this issue, though sometimes I get
this message upon trying "svn cleanup" on a path affected by the
"bumping revisions" error:
In directory 'C:\Some\WC\Path'
Error processing command 'modify-entry' in 'C:\Some\WC\Path'
When I check the log or "svn info" on any affected path, it always
looks like this:
Repository Root: svn://subversion-server/repo
Repository UUID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Node Kind: file
Last Changed Author: username
Last Changed Rev: 28487
Last Changed Date: 2007-05-02 10:48:05 -0700 (Wed, 02 May 2007)
One strange thing is the "-0700" -- we are PDT, so shouldn't it be
"-0800"? Otherwise, the time looks correct.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed May 2 21:14:15 2007