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

Linux working copy through SAMBA

From: Giulio Troccoli <Giulio.Troccoli_at_uk.linedata.com>
Date: Wed, 28 May 2008 10:01:02 +0100

Sorry for the cross-posting but I'm really not sure whether this is a
question more suitable for the TortoiseSVN mailing list or for the SVN
mailing list.

Our Subversion server is a Linux box with SVN 1.4.4 and Apache 2.0.

The Web Team uses another Linux box as their development server and each
developer has a working copy. This box has SVN 1.4.4.

However all their work is done on their PCs, accessing their WC using
TortoiseSVN (1.4.5) and a SAMBA mounted drive. Once a changed is
committed they can tested straight away on their PC. Basically they
never work on the test linux box.

From time to time we have problems with their working copies. It can be
that Subversion cannot access a .lock file (sorry I can't remember the
exact message), or that Subversion thinks that a directory is not a
working copy (although the .svn directory hasn't been touched). I
usually end up taking a copy of the offending file/directory, delete it,
do an update and restore it.

Does anybody know why this could happen? I usually see this problem when
the WC is on a Windows box and the AV interferes with it, but this is
not the case. I don't know SAMBA that much, could that cause the

I'm also working on a different solution, which involves installing a
VNC server of the linux box so that they can connect to it and use KDE
or GNOME, but I need to find a GUI client for them. Does anybody know

Linedata Services (UK) Ltd
Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB
Registered in England and Wales No 3027851 VAT Reg No 778499447

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-28 11:01:49 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.