> -----Original Message----- > From: KARR, DAVID (ATTSI) [mailto:dk0...@att.com] > Sent: 14 January 2011 19:07 > To: Tony Sweeney; users@subversion.apache.org > Subject: RE: SVN 1.6.15 checkout fails on particular file > > > -----Original Message----- > > From: Tony Sweeney [mailto:tswee...@omnifone.com] > > Sent: Friday, January 14, 2011 10:57 AM > > To: KARR, DAVID (ATTSI); users@subversion.apache.org > > Subject: RE: SVN 1.6.15 checkout fails on particular file > > > > You can't mix Subversion client releases where the middle > digit of the > > version number differs. Subversion clients are backwards > compatible > > when talking to the server, but not when writing workspace > metadata to > > the filesystem. You can, in theory, use whatever version > you like on > > the client side against any server version. However, when > you invoke > a > > client on a workspace, it checks to see if the local > metadata is the > > same version as itself, and if it discovers an older > version, silently > > upgrades the format to its own. At this point, older > clients will no > > longer work on that workspace. > > Just so we're clear here, I have these projects checked out > in Eclipse, but not in the same directory that I'm trying to > do the command-line checkout. I'm trying to do a separate > checkout of these projects, just using the 1.6.15 client. > I'm not using multiple client versions in the same > checked-out directory, but I am attempting to checkout a > module from SVN with the 1.6.15 client that has been > previously checked out with different client versions. > > Is the conflict in mixing client versions relevant to the > module in the server, or in the client-side directory? If > it's the latter, then there should be no conflict, as I'm > only using the 1.6.15 client in this directory. >
Only in the client. If your workspaces are disjoint then that should have worked. Subversion doesn't keep any record of workspace state (more's the pity). Tony.
