2011/5/11 Dave Tingling <dave.tingling_at_infotechfl.com>:
> Hi List,
>
> We administer subversion (v 1.4.2, r22196 on CentOS 5.5) for a development
> company, and have over 150 active repositories, but we are not subversion
> experts. We are experiencing an issue with just one particular repository.
>
> When programmers run an update against this one repository (using either
> TortoiseSVN 1.6.15 or Slik Subversion 1.6.16 on Windows 7 Pro SP1), they
> observe that they sometimes get---to coin their term---"frankenstein"
> versions of arbitrary files. As an example scenario:
>
> 1) - Developer A: adds, edits and commits a file X,
> 2) - Developer A: later, again edits and commits file X,
> 3) - Developer A: still later, again edits and commits file X,
> 4) - Developer N: who has never before seen file X, runs an update. She gets
> a weird version of file X which contains only *some* lines of the set of
> changes made by Developer A in each of the edit/commit sessions (1), (2),
> and (3).
>
On client: it is easy to break one's working copy if you move
directories around mindlessly.
One should always use svn command when moving around directories, and
never the system commands.
http://tortoisesvn.net/mostforgottenfeature.html
On *nix that is the difference between "mv" and "svn mv". If you mv a
directory the ".svn" subdirectory of it is moved along, but still
points to the old location. Trying to commit any file in the moved
directory will actually commit it to the original location, because of
that stale ".svn" subdirectory.
The "svn info" command (or Subversion tab in file properties dialog in
Windows Explorer on a PC where TortoiseSVN is installed) what is
repository path for any particular file in the working copy.
On the server: what protocol you are using to access the repository and
commit the files? I hope there is no proxy in between you and client,
that performs some sort of url rewriting?
> We administer subversion (v 1.4.2, r22196 on CentOS 5.5)
Anyway, 1.4.2 is very old, and misses a number of fixes in 1.4.x line,
not to mention the later versions. In some other thread recently when
"CentOS 5.5" was mentioned one of the answers was to upgrade to 5.6
ASAP.
Best regards,
Konstantin Kolinko
Received on 2011-05-11 22:15:48 CEST