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

RE: Re: Re: 1.9 fails commits on repos checked out previously on 1.8.x

From: Jamie Wardlaw <jwardlaw_at_unifire.ca>
Date: Wed, 9 Sep 2015 00:37:29 +0000

OK, thanks for the clarification.

I think this would be why my command line operations never failed as I have slikSVN v 1.8.10 at present i.e. I’ve not updated that to a 1.9 based client library yet.


From: Simon Large [mailto:simon.tortoisesvn_at_gmail.com]
Sent: September-08-15 12:02 PM
To: users_at_tortoisesvn.tigris.org
Subject: RE: Re: Re: 1.9 fails commits on repos checked out previously on 1.8.x

On 8 Sep 2015 18:34, "Jamie Wardlaw" <jwardlaw_at_unifire.ca<mailto:jwardlaw_at_unifire.ca>> wrote:
> Hello,
> So it looks like over the weekend people reached a conclusion that this is in fact a problem with the SVN server as opposed to TSVN.

No, that's not the conclusion at all. It is a subversion 1.9 client problem with working copies on a network share. Neither the server not the repository comes into it. It seems to be network shares in SMB1 format, which are primarily hosted by xp and some windows server versions.

> In my case, our SVN server is located on a standalone machine, win 7, running SubversionEdge from Collabnet v4.0.12 with SVN 1.8.11
> We do have working copies on network shares and never in 3+ years have seen any issues working this way.

That's because you have not been using a1.9 client.

> Am I correct in saying that TSVN is not the root cause of the problem and we have now identified that the SVN server needs to run off 1.9.2?

SVN client library 1.9


> Just seems strange to me that this is the problem when I am runnign a server with SVN 1.8.11 integrated and it has been like that for quite some time.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-09-09 02:37:39 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.