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

revisions not in sync, svn won't let me update.

From: Jeff S <sffej_at_yahoo.com>
Date: 2006-10-06 20:32:45 CEST

Moved from svn 1.0.x to 1.4. The dump file was loaded

unto new svn. Other developers had commits that were
not included in the dump file that was loaded for the
new svn.

They are now getting error that revisions are not in
sync, and svn won't let me update.

Tried to do another dump of orignal repo but the new
install of svn complains that the version of BerkelyDB
no longer matches - so I cannot get dump file.

They are trying to commit at revison 2651 but the
loaded svn repo is back at revision 2644. How can I
force the svn repo or client working copy revision
levels to match up for a commit? Or is there
another way to handle this?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 6 20:37:28 2006

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.