I'm experiencing some strange behavoir with subversion 1.1.3 on Linux.
A while back I started a subversion repository with a script that
checked in a year's worth of code changes, and now I want to go back and
set the author to "unknown" so that it's obvious for the old code that
it wasn't all mine.
Here's the interesting part:
bash$ for ii in `seq 3 35`; do svn propset -r $ii \
--revprop svn:author "unknown"; done
property 'svn:author' set on repository revision 3
property 'svn:author' set on repository revision 4
property 'svn:author' set on repository revision 5
/ snip many lines /
property 'svn:author' set on repository revision 25
property 'svn:author' set on repository revision 26
property 'svn:author' set on repository revision 27
svn: Connection closed unexpectedly
svn: Can't connect to host 'blah.blah.com': Connection refused
svn: Can't connect to host 'blah.blah.com': Connection refused
svn: Can't connect to host 'blah.blah.com': Connection refused
svn: Can't connect to host 'blah.blah.com': Connection refused
If I try to run it again immediately, I immediately get "Connection
refused" messages. If I run "svn status", it resets and I can again run
27 propsets before it blows up. So that says to me that it's not a lack
of file descriptors or something... it must be related to Subversion.
It's connecting to svnserve on the same machine.
Any ideas?
Thanks, Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 3 02:11:47 2005