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

Re: Subversion version confusion.

From: Andy Levy <andy.levy_at_gmail.com>
Date: Fri, 3 Apr 2009 09:35:11 -0400

On Fri, Apr 3, 2009 at 09:15, James Green <James.Green_at_occam-dm.com> wrote:
> Thanks for this Andy.
>
> I've basically disabled Ankh in VS for the time being.  TortoiseSvn is the preferred option anyhow.
>
> Seems that I need to apply more version control rather than just blindly updating when a new version become available.

Absolutely. I'm holding off on deploying TSVN 1.6 due to some bugs
there; I also have need for 4 clients (command-line, TSVN, AnkhSVN &
Subclipse) on my own workstation, and I need to make sure the
distributions are all up to 1.6 before I can even think about it.

There's nothing wrong with staying a couple weeks behind behind if the
"old version" is working well.

> -----Original Message-----
> From: Andy Levy [mailto:andy.levy_at_gmail.com]
> Sent: 03 April 2009 14:04
> To: James Green
> Cc: users_at_subversion.tigris.org
> Subject: Re: Subversion version confusion.
>
> On Fri, Apr 3, 2009 at 08:33, James Green <James.Green_at_occam-dm.com> wrote:
>> Hi All,
>>
>> I've just added a new solution to a repo on our svn server (Visual SVN
>> 1.6.3) which I believe is using Svn 1.5 ...
>>
>> I added the solution to SubVersion using TortoiseSVN 1.6.0, Build 15855.  I
>> also have the AnkhSvn plugin installed.  Now in VS everything is marked with
>> a blue + sign and basically VS thinks this is all outside of Svn ... so I
>> initially started to go through the commit thing again and then I got an
>> error that told me to go to this page:
>>
>> http://subversion.tigris.org/faq.html#working-copy-format-change
>
> Did you upgrade AnkhSVN to a version compatible with SVN 1.6 when you
> upgraded TSVN?
>
>> I must admit that I find a lot of docs and pages on the Svn site to be more
>> confusing than helpful.  This is all telling me that my CLIENT
>> (Tortoise/Ankh) is out of date, whereas its the clients that are the most up
>> to date and the Visual SVNServer is probably the oldest version we have ...
>
> If you touch a WC with multiple clients, all those clients must be
> built on the same major.minor SVN libraries due to WC format changes.
>
>> Do I actually need to upgrade the Visual Svn Server software???
>>
>> Is this actually a bug somewhere or can someone explain this to my confused
>> brain?
>
> Client & server versions are independent as long as you stay within
> 1.x. Newer features will be partially or completely disabled depending
> upon what versions you have in the mix, but with a 1.5 server
> (VisualSVN Server 1.6 is SVN 1.5) and 1.6 clients, there's no change
> in functionality.
>
> scanned by MessageLabs [www.messagelabs.com]
>
>
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1532365

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-03 15:37:11 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.