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

Reorganized repository, cannot update

From: Tristan Seligmann <tristan_at_quotemaster.co.za>
Date: 2003-12-15 09:40:07 CET

(In the rest of this e-mail, ROOT refers to the root of the repository,
http://server.local:8080/svn/qm)

Originally, I setup the repository with the following structure:

ROOT/trunk/qmaster/
ROOT/branches/qmaster/...
ROOT/tags/qmaster/...

created by cvs2svn.py from our original CVS repository. I decided now
that this structure was a bit odd, and decided to use cvs move on the
repository (actually through the TSVN repository browser) in order to
achieve the following layout:

ROOT/qmaster/trunk/
ROOT/qmaster/branches/...

('tags' got deleted shortly after checkout, as there was no longer
anything relevant in there).

Now, everyone else just had a working copy with a checkout of
ROOT/trunk/qmaster/; when they try and run an update on this working
copy, the following error occurs:

REPORT request failed on '/svn/qm/!svn/vcc/default'

svn_repos_dir_delta: invalid edit anchoring; at least one of the input
paths is not a directory, and there was no source entry.

My guess is that this occurs because the 'qmaster' directory has been
moved to a location that doesn't exit in their working copy. How can I
work around this? If I could 'expand' their working copy to contain the
entire tree instead of just the subdir it currently consists of, I
suspect that would solve the problem; any workaround would be fine,
though. I would prefer not to go through deleting the wc and checking
out a new one, as there are changes in these working copies that need to
be preserved.

Any ideas?

Tristan Seligmann

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 15 09:39:46 2003

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.