I think you should be using svn+ssh. http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.serverconfig.svnserve.sshauth Doing it this way ensures that everyone is using the same version if you set up your ssh shell access paths properly. Also, you can upgrade the version on the server and everyone will be upgraded since this svn+ssh protocol actually runs svnserve on the server from the path you speicify.
But, that doesn't really matter. Once you have created the repository with the version you are using accessing it via the file:// protocol with TSVN will not change its format.
In other words, if you have an existing repository that you use TSVN on you shouldn't have a problem. If you create a repository with TSVN 1.6.x then try to access it with 1.4 clients via file protocol, then yes, you will have problems.
BOb
> I'm using file:// 'cause all of the setup instructions I found for using
> svn over SSH that I saw do it that way. Our setup is a 'file server'
> which I access over the internet using SSH while the others who use it
> are on the server's local network. Everything is locked down pretty
> tight, there is no http access, only https. What do you suggest?
>
> Bob Archer wrote:
> >> I have had trouble in the past using Tortoise on the server then
> >> accessing the repository over the internet. There seems to be a lot of
> >> dependency on versions. I currently am using 1.4.4 with Apache 2.2.4.
> >> When the person who initially loaded the archive did it he was using
> >> Tortoise with a network mounted drive and we found that the file format
> >> value (in the format file) was not compatible with the server setup.
> >> Currently, format contains a 5. Can I use the latest Tortoise or do I
> >> need to load an older one?
> >>
> >> BTW, thanks for your patience. This is my first attempt at setting up
> >> and administering subversion and I realize some (if not all) questions
> >> are basic. I have looked over the documentation but because the
> >> repository was not set up according to the recommended structure,
> things
> >> don't seem to work as they I expect.
> >>
> >
> >
> > Ok, I see the problem... I set up a repo and tested this my self. If you
> try to copy it all to trunk then there is a problem.
> >
> > I was able to move the folders/files one at a time. Like this:
> >
> > svn mkdir file:///c:/Users/Development/TestRepository
> >
> > svn mv file:///c:/Users/Development/TestRepository/folder1
> file:///c:/Users/Development/TestRepository/trunk
> >
> > repeat for each folder/file in the root of your project.
> >
> > Here is another way... you will need svnadmin to do it... You well need
> to create a new empty repository...
> >
> > mkdir TempDump
> > cd TempDump
> > svnadmin dump c:/Users/Development/TestRepositry > MyRepo
> > svnadmin load --parent-dir c:/Users/Development/NewRepository/Trunk <
> MyRepo
> >
> > Ah yes, you have to be careful with versions. I really suggest you use
> 1.6 for everything. Also, you really shouldn't be using the file://
> protocol on shared repositories.
> >
> > BOb
> >
> > ------------------------------------------------------------------------
> >
> >
> > No virus found in this incoming message.
> > Checked by AVG - www.avg.com
> > Version: 9.0.814 / Virus Database: 271.1.1/2840 - Release Date: 04/28/10
> 02:27:00
> >
> >
>
> --
> Steve Kelley
> 106 Oklahoma Ave.
> Oak Ridge, TN 37830
> 865 482 7131
Received on 2010-04-28 18:58:42 CEST