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

After renaming directories and commiting, unable to update remote working copy

From: <me_at_johnea.net>
Date: Wed, 4 Jun 2008 16:48:19 -0700 (PDT)

Hi all,

The affected repository has been in service for about 2 years.

The primary usage is for me to commit my local working copy to the server,
and then the content is updated on a remote workstation's working copy.

This has been working very well.

Recently the sub-directories within the working copy for several evolving
projects were renamed via svn mv on my local working copy and committed as
usual. However when the remote user attempted to update a variety of
errors occurred. Today onsite at the remote location I attempted a number
of manuvers to encourage svn to update the working copy.

My last attempt was simply to rename the local working copy and
re-checkout the entire repository. That added a list of files and
eventually crashed with the following error message:
A johnea/project04-Menon/pp/pretty-packet
A johnea/project04-Menon/pp/Q.pkt
A johnea/project04-Menon/pp/pretty-packet.c
svn: In directory 'johnea/project04-Menon/pp'
svn: Can't move source to dest
svn: Can't move
'johnea/project04-Menon/pp/.svn/tmp/prop-base/u.pkt.svn-base' to
'johnea/project04-Menon/pp/.svn/prop-base/u.pkt.svn-base': No such file or

The directory pp/ has been at the center of all issued error messages. The
original update failed saying this directory was locked or that a certain
file within this directory was not a working copy, or that the same file
failed executing modify-wcprop. The file complained about has binary data.

My originating local working copy is from a linux workstation running svn
1.4.5 on the command line.

The server is FreeBSD running svn server 1.3.0

The receiving/updating workstation is windows running tortoiseSVN 1.4.5
and cygwin command line svn 1.4.5.

At first, since the trouble originated on the windows platform I thought
the issue could be TortoiseSVN related, but today I used only cygwin
command line svn and receivedd the same error messages.

This all seems to have stemmed from renaming the directories within the
repository. Even when I originally issued the svn mv commands on my local
linux working copy and committed the results I had the odd experience of
having to then update my local copy before my changes appeared there.

I've been attempting to debug this for several days now and am running out
of ideas. Any help understanding what's going on are very gratefully


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-05 07:13:04 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.