On Sat, Nov 17, 2012 at 6:25 AM, Andy Levy <andy.levy_at_gmail.com> wrote:
> On Sat, Nov 17, 2012 at 3:41 AM, Guido Leenders
> <Guido.Leenders_at_invantive.com> wrote:
>> We are using SVN 1.7.7 (TortoiseSVN 1.7.10) on Windows and SVN 1.7.7 on
>> Linux with Samba against the same working copies. The working copies are
>> located on the home directory of the user (/home/XXX or h:\).
>> Reason for such dual use is that some build software runs only on Windows
>> and some only on Linux and there are no really reliable platform crossing
>> This worked fine with SVN 1.6, but since a few weeks we are working with
>> 1.7. We have tested 1.7 in our setup for months on a Windows only laptop and
>> working copies had little to no problems.
> This is an unsupported and not-at-all recommended or encouraged scenario. If
> it worked in the past, you were fortunate; no guarantees were ever made that
> it would work, so breakage should not be unexpected.
> Never share working copies between OSes or users. Best practice has always
> been one WC per OS per user.
> There is no way to "overcome this" aside from stopping the activity
If this is a misuse, it is a quite common misuse. A quick google
search turned up:
I've always had the impression, which I've shared with others, that an
SVN working copy is just a set of files you can copy around and access
from multiple systems like any other set of files.
Other revision control systems work certainly don't complain if you
use the same client version to interact with the some working copy on
two different OSes. SVN doesn't normally, either.
I understand that this particular case is from a user using two
DIFFERENT versions of SVN, but it is VERY unexpected that the SAME
version would cause problems. That's like opening a jpeg in an image
editor on Linux and getting errors when opening the same jpeg in the
same program on Windows.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-11-20 01:36:12 CET