[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn: Bogus date

From: Jared Hardy <jaredhardy_at_gmail.com>
Date: 2007-07-07 01:22:25 CEST

So I finally got some new information about this "Bogus date" error.
It only happens when a user commits a file with a lock, and when they
don't keep the lock upon commit. If the user selects --no-unlock, or
the "keep locks" checkbox in TortoiseSVN, the "Bogus date" error never
comes up. If they release the lock later, without committing again,
there is no error at all. So the "Bogus date" error only occurs when
an unlock and commit operation happen simultaneously.
    In addition to the versions stated in the original e-mail about
this issue, some users are still getting this error when using Win32
version 1.4.4.

    I hope this helps,

On 4/30/07, Jared Hardy <jaredhardy@gmail.com> wrote:
> We recently changed subversion servers, and a week into using it, and
> now a random subset of my users are getting this error, esp. 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. Has anyone had a similar problem? Any
> recommended fixes? 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.
> Jred

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 7 01:22:23 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.