svn: Bogus date

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-unsubscribesubversion.tigris.org
For additional commands, e-mail: users-helpsubversion.tigris.org

On Apr 30, 2007, at 14:25, Jared Hardy 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.

I see this question has come up a couple times before.
There's one  
thread here which suggests the problem originated from
converting a  
VSS repository to Subversion with vss2svn:

http://osdir.com/ml/version-control.subversi
on.vss2svn.user/2005-09/ 
msg00005.html

Did you use vss2svn originally? As in several years ago?
From the  
thread above, it looks like there may have been a bug in
vss2svn.  
Perhaps new versions of Subversion are more picky about
this.



-- 

To reply to the mailing list, please use your mailer's Reply
To All  
function


------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubversion.tigris.org
For additional commands, e-mail: users-helpsubversion.tigris.org

On 4/30/07, Ryan Schmidt <subversion-2007bryandesign.com> wrote:
> I see this question has come up a couple times before.
There's one
> thread here which suggests the problem originated from
converting a
> VSS repository to Subversion with vss2svn:

Nope. This repository was converted from CVS via cvs2svn
over a year
ago. This is the first upgrade since then. I changed servers
by
completing a standard "svnadmin dump" off the old
svn1.2 SLES 9
server, and an "svnadmin load" on the new svn1.4.3
SLES 10 server. I
retained the same server name and path on the new server.
The really
strange thing is that we had been working with the new
repository
trouble-free, for almost a full week, when this started
happening. It
only seems to affect certain users, after the first time
they "svn
add" any new files. As I said, the update/resolve cycle
seems to fix
the problem until the next commit, so we are using that as
a
work-around.
    This problem seems to be completely on the Working Copy
side,
since only the committer is ever affected. All the
information I have
seen related to the "Bogus date" error seems to
indicate it is a
server/repo issue, but the dates look correct when I look
through the
logs. Here is a small snippet of recent log lines:

------------------------------------------------------------
------------
r28442 | user1| 2007-04-30 16:28:13 -0700 (Mon, 30 Apr 2007)
| 1 line
------------------------------------------------------------
------------
r28441 | user2 | 2007-04-30 16:27:33 -0700 (Mon, 30 Apr
2007) | 1 line
------------------------------------------------------------
------------
r28440 | user1| 2007-04-30 16:21:18 -0700 (Mon, 30 Apr 2007)
| 1 line
------------------------------------------------------------
------------
r28439 | user1| 2007-04-30 15:51:47 -0700 (Mon, 30 Apr 2007)
| 1 line

Note that "user1" is seeing the error, while
"user2" is not. Names are
changed to protect the innocent, and extra newlines are
taken out, but
otherwise this is a verbatim copy of output from "svn
log
svn://subversion/repo".

Jred

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubversion.tigris.org
For additional commands, e-mail: users-helpsubversion.tigris.org