1.7 compatibility issue

2011-07-26 Thread Becker, Thomas
Hi, I tried to list a repository served by Visual SVN 2.1.9 (Subversion 1.6.17, Apache 2.2.19) with a Windows 1.7 pre-release client downloaded from Collabnet (https://ctf.open.collab.net/sf/frs/do/viewRelease/projects.csvn/frs.svn _binaries.windows ). With the "alpha" and "beta" clients I

Re: 1.7 compatibility issue

2011-07-26 Thread Ivan Zhakov
On Tue, Jul 26, 2011 at 12:34, Becker, Thomas wrote: > Hi, > > > > I tried to list a repository served by Visual SVN 2.1.9 (Subversion 1.6.17, > Apache 2.2.19) with a Windows 1.7 pre-release client downloaded from > Collabnet > (https://ctf.open.collab.net/sf/frs/do/viewRelease/projects.csvn/frs.s

AW: 1.7 compatibility issue

2011-07-26 Thread Becker, Thomas
compatibility issue On Tue, Jul 26, 2011 at 12:34, Becker, Thomas wrote: > Hi, > > > > I tried to list a repository served by Visual SVN 2.1.9 (Subversion 1.6.17, > Apache 2.2.19) with a Windows 1.7 pre-release client downloaded from > Collabnet > (https://ctf.open.collab.n

Re: 1.7 compatibility issue

2011-07-26 Thread Mark Phippard
On Tue, Jul 26, 2011 at 4:34 AM, Becker, Thomas wrote: > Hi, > > ** ** > > I tried to list a repository served by Visual SVN 2.1.9 (Subversion 1.6.17, > Apache 2.2.19) with a Windows 1.7 pre-release client downloaded from > Collabnet ( > https://ctf.open.collab.net/sf/frs/do/viewRelease/proje

AW: 1.7 compatibility issue

2011-07-26 Thread Becker, Thomas
@subversion.apache.org Betreff: Re: 1.7 compatibility issue On Tue, Jul 26, 2011 at 4:34 AM, Becker, Thomas wrote: Hi, I tried to list a repository served by Visual SVN 2.1.9 (Subversion 1.6.17, Apache 2.2.19) with a Windows 1.7 pre-release client downloaded from Collabnet (https

Re: 1.7 compatibility issue

2011-07-26 Thread Mark Phippard
On Tue, Jul 26, 2011 at 11:44 AM, Becker, Thomas wrote: > Sorry for the confusion: stands for svn/, stands for > . The URL looks like https:// > :8443/svn/. > So you are saying you cannot even do svn ls against a repository? The automated test suite would exercise that. It could be s

Re: 1.7 compatibility issue

2011-07-26 Thread Ivan Zhakov
On Tue, Jul 26, 2011 at 13:37, Becker, Thomas wrote: > Yes, actually starts with svn. The URL looks like this: > https://:8443/svn/ > > Regards, >  Thomas > Could you please try to add explicit ServerName configuration directive to "%VISUALSVN_SERVER%\conf\httpd-custom.conf" file and restart

Re: 1.7 compatibility issue

2011-07-26 Thread Ivan Zhakov
On Tue, Jul 26, 2011 at 20:25, Ivan Zhakov wrote: > On Tue, Jul 26, 2011 at 13:37, Becker, Thomas wrote: >> Yes, actually starts with svn. The URL looks like this: >> https://:8443/svn/ >> >> Regards, >>  Thomas >> > Could you please try to add explicit ServerName configuration > directive

Re: 1.7 compatibility issue

2011-07-26 Thread Ivan Zhakov
On Tue, Jul 26, 2011 at 20:45, Ivan Zhakov wrote: > On Tue, Jul 26, 2011 at 20:25, Ivan Zhakov wrote: >> On Tue, Jul 26, 2011 at 13:37, Becker, Thomas >> wrote: >>> Yes, actually starts with svn. The URL looks like this: >>> https://:8443/svn/ >>> >>> Regards, >>>  Thomas >>> >> Could you

AW: 1.7 compatibility issue

2011-07-27 Thread Becker, Thomas
: Dienstag, 26. Juli 2011 18:17 An: Becker, Thomas Cc: users@subversion.apache.org Betreff: Re: 1.7 compatibility issue On Tue, Jul 26, 2011 at 11:44 AM, Becker, Thomas wrote: Sorry for the confusion: stands for svn/, stands for . The URL looks like https://:8443/svn/. So you are