DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=fpCULGSwatMnxLphN63xH53MWPomInKrG60z+TIdN3U
	o4U5uKD6Q4TM7szM3B36O+OcfI+jMTV0dz6w0p5F/GN8nLuWmAHpqcyOax44TlGM
	BEr99GiyqK5f12ctYPGDtsuqTM8xru8WPJbpMFJjIHolu/5ixxf2lVTDjAo9VqPk
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <52894C42.3070704@tiscali.co.uk>
Date: Sun, 17 Nov 2013 23:07:46 +0000
From: David Stacey <drstacey@tiscali.co.uk>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: : Subversion packages
References: <CAFMYRRMFGxJhMKNKVgUEs45Lb5dLCf-5vq+Rp5s0H=Eg1yB5kw@mail.gmail.com> <CAFMYRRPZWqSJWZVVGDQLLZ55ZOcD_H9q7UgPr4iZyKw9vr2TbQ@mail.gmail.com> <52890843.90903@acm.org> <20131117194958.GA4006@ednor.casa.cgf.cx> <174472546.20131118011119@mtu-net.ru>
In-Reply-To: <174472546.20131118011119@mtu-net.ru>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 17/11/13 21:11, Andrey Repin wrote:
> Normally, you can expect Subversion to transparently operate across different
> mix of client and server versions, but they've made a... change[1]... back in
> the days, that made working directories illegible in newer (1.7+) clients.
> The 1.7 client has the means of converting 1.6 working directories to a new
> format. I'm unsure, if 1.8 still have this ability.

You are correct - you can mix different versions of the svn client and 
server. For instance, I have used svn-1.7 and svn-1.8 clients with a 
svn-1.6 server without any difficulty. However, if the server is an 
earlier release than the client then you may not enjoy some of the new 
benefits that the client offers.

Escaping the svn-1.6 client can be quite tricky, as it is embedded into 
many different development products and plugins. However it is worth the 
effort, and I would encourage the OP to upgrade if possible. The fact 
that svn-1.6 is no longer supported will be an incentive for most companies.

If anyone is genuinely unable to upgrade and desperate for a Cygwin 
svn-1.6 client then there is always the Cygwin Time Machine - surely 
this is preferable to the considerable effort of maintaining parallel 
svn installations.

Regarding you second point: The svn-1.7 client introduced a new working 
copy format, and you had to 'svn upgrade' your old svn-1.6 working 
copies. Once a working copy has been upgraded, it can then only be used 
with a svn-1.7 client. The same is true when upgrading the client from 
svn-1.7 to svn-1.8: the working copy must be upgraded again, and once 
upgraded the working copy can only be used with a svn-1.8 client. All of 
this is independent of the server version.

In theory, it is possible for a svn-1.8 client to upgrade a svn-1.6 
working copy, although I've not attempted this personally.

Dave.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple