On 17.08.2010 20:07, Eric wrote:
> Using TSVN 220.127.116.1198 on WinXP Pro SP3 and SVN 18.104.22.16896 on
> CentOS Linux 5.
> From time to time, especially on large commits, I find that when the
> SVN server finishes the commit (and sends me an email telling me it
> has finished with the commit), TSVN doesn't get the word that the
> server has finished, and it sits there forever waiting for word that
> the commit is done and TSVN can display the version number and
> activate the OK button to exit.
> Since TSVN doesn't get the word that the commit was successful, it
> doesn't do whatever it does to update the .svn directories. So, if I
> terminate TSVN and then try to do an update, I get a bunch of
> conflicts. However, if I take the directory I just committed and
> move it to another directory tree, and then do a TSVN Update to
> restore it to my sandbox, I find that the files I just restored and
> the files I just committed are identical, so I know the commit was
> Is this an incompatibility between TSVN 1.6 and SVN 1.4? I can't
> upgrade the server; do I need to downgrade the client?
I would guess that this has to do with your network connection or server
setup. Try to increase the timeout values on your server.
And check firewalls and proxies for the same.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-08-17 20:13:03 CEST