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

RE: Re: svn: Bogus date

From: Srilakshmanan, Lakshman <lakshman.srilakshmanan_at_police.vic.gov.au>
Date: 2007-07-10 02:14:39 CEST

Hi Jared,

I have been reading this issue, on dev and user mail archive, with keen
interest. I have used Subversion 1.3.x for a year and a half with no
issue while adding new directory or files
http://svn.haxx.se/dev/archive-2007-05/0123.shtml or removing the lock
on commit http://svn.haxx.se/users/archive-2007-07/0115.shtml.

1. Is this an issue experienced in 1.4.x ?
2. Is this an issue experienced in the combination of 1.4.x and Suse ?

The reason I am asking the above questions is because I plan to install
svn_1.4.3 on RedHat Rel 4 soon. I am wondering whether I should use
svn_1.3.x instead.

Your thoughts and feedback will be appreciated.


-----Original Message-----
From: Jared Hardy [mailto:jaredhardy@gmail.com]
Sent: Saturday, 7 July 2007 9:22 AM
To: users@subversion.tigris.org; dev
Subject: Re: svn: Bogus date

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

    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: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

The information contained in this email and any files attached may
be confidential information to the intended recipient and may be
the subject of legal professional privilege or public interest immunity.

If you are not the intended recipient, any use, disclosure or copying is

If you have received this document in error please telephone 1300 307 082

This footnote also confirms that this email message has been swept
for the presence of computer viruses.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 10 02:15:53 2007

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

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