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

Re: Upgrade to v1.7 = death of working copies

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Fri, 11 May 2012 11:32:06 +0200

On Fri, May 11, 2012 at 11:12 AM, Thorsten Schöning
<tschoening_at_am-soft.de> wrote:
> Guten Tag Julius Smith,
> am Freitag, 11. Mai 2012 um 08:45 schrieben Sie:
>> My experience was different - I could not check into the 1.6 server
>> on Linux (with 1.6-format repo) from my 1.7-upgraded working copy
>> (with 1.7 svn client) on the Mac.
> Than your experience is wrong

Except if you're working with the file:// protocol (and accessing an
NFS-mounted repository that's used from both machines (running
different svn versions) or something like that), which means the
client directly manipulates the repository. If that's the case ... you
shouldn't do that (only for testing / POC uses, and only if you use it
from a single machine). Use a real server (svnserve or
apache+mod_dav_svn), and you shouldn't have any interoperability
problems (client and server communicate via defined protocols which
are fully compatible accross versions).

>, you got an error and should give
> detailed information about that.

But whatever the issue, the above is always important. People can't
help you unless you tell them in detail what happened. Don't start
assuming things too quickly ...

Received on 2012-05-11 11:33:01 CEST

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