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

Large Commits Fail

From: Rob Wilkerson <r.d.wilkerson_at_gmail.com>
Date: 2006-08-19 12:20:15 CEST

Can someone help me understand why I can't seem to perform large-scale
commits? Is this a limitation of Subversion? I have a reasonably
large - but not crazy - repository (roughly 3,000 files). I just set
svn:keywords on all files from the root and that worked great. When I
try to commit, however, the commit fails. If I try the same commit
multiple times, the reason for the failure changes frequently. The
"location" of the error (at least where it's reported in the commit
process) changes every single time.

Sometimes I get this:
At least one property change failed; repository is unchanged

Sometimes I get this:
CHECKOUT of '/repos/myproject/!svn/ver/16/branches/dev/tahoe-code-reorg/.java/src/com/wintertree/ssce/PropSpellingSession.java':
could not connect to server (http://vm-seprojects)

There are one or two others that make an appearance, too, but I don't
have access to those at the moment. Considering the inconsistency
with which I get them and the locations in which they're reported, the
message itself may (or may not) be terribly important.

Seems like doing several smaller commits solves the problem, but
that's not really much of a solution.

This has happened to me before on large commits and I've never been
able to figure it out. Anyone have any thoughts?

Rob Wilkerson
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Aug 19 12:21:32 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.