> Is there anything common to those folders like e.g. that they use
> characters outside the ASCII range?
No. They should be correct encoded because SVN 1.6.x client shows correct behaviour. But I am not shure because I do not know a way to check for proper encoding.
> > The server is a VisualSVN with SVN server 1.6.x.
> "SVN server"? You don't mean svnserve, which wouldn't have an
> "apache.log". In particular, you are not using "svn://.." URL but
> "http://.." or "https://..", right?
It is a VisualSVN on a Windows Server. Any yes, I am using https:// with NTLMv2 authentication.
> > [Fri Jan 11 10:13:29 2013] [notice] Apache/2.2.22 (Win32) DAV/2 SVN/1.7.5 mod_ssl/2.2.22 OpenSSL/0.9.8x configured -- resuming normal operations
> > [Fri Jan 11 10:13:29 2013] [notice] Server built: May 18 2012 14:18:09
> Something is inconsistent here: It says "SVN/1.7.5" while you claim you
> are using 1.6. Check which ones are really installed and running.
You are right. The server runs in backward to 1.6.x compatible mode (we need the directory .svn in every folder to be able to provide all project's trunc on a specific network drive). Could this be the source of the issue?
> Also, 1.7.5 is a bit old already and there's been a bunch of bugfix
> releases since its release.
Maybe the error comes from VisualsSVN. I will check this with my System Administrator. Latest release is VisualsSVN 2.5.8 with Subversion 1.7.8. He promised me to update the server. I will respond as soon as he has done the update and I can try the different versions of TortoiseSVN clients (1.6.x vs. 1.7.11).
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-01-16 11:49:22 CET