I wrote to the users list to see if anyone had seen anything like this
before. I had no useful responses there, and there doesn't seem to be
any similar issue in any mailing list archive, nor the issue tracker.
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
Having them update and resolve recursively seems to get them around
this, but it's still annoying. In some cases where the user has added
a new file, it also automatically puts that user in the "file already
exists" error situation. Has anyone had a similar problem? Any
recommended fixes? If not, I think this should be added as an official
Issue.
Servers and clients are all 1.4.3, Suse LES 10
server, Win XP SP2 clients. Some clients recently upgraded from 1.3.0,
but all clients have the same messages regardless of upgrade path.
The current repository was "svnadmin load"ed from a dump created on
the old server, svn v.1.2.0. There were no errors on any dump or load.
"svn switch" was not necessary because the new server retained the
exact same address, paths, and repository IDs as the old server.
I have run "svn log -r XXXX" and "svn info -r XXXX" on all
affected paths and revisions, and I never get that "Bogus date" error
message any time other than on commit.
Jred
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 2 02:02:26 2007