> -----Original Message-----
> From: Ryan J Ollos [mailto:ryano_at_physiosonics.com]
> Sent: dinsdag 12 april 2011 0:36
> To: dev_at_subversion.apache.org
> Subject: SVN reports that all targets are not part of same working copy
> there is an svn:external that points within the repository
> I originally reported this issue with TortoiseSVN , but we narrowed it
> down to an issue in Subversion 1.7dev.
> If I am committing a working copy with modifications to dir1 and dir2,
> being an svn:externals directory that points to a location *within* the
> repository, I get an error that I didn't see with SVN 1.6:
Subversion 1.5/1.6 didn't do proper lock checking when committing, which
allowed you to commit nested working copies when a few preconditions where
true. (I reported this issue with some examples on how this could corrupt
your working copy beyond repair when we were working on Subversion 1.6).
The new working copy library isn't as sloppy as the old working copy library
(aka WC-)1.0 and correctly detects that the files are not in one working
copy and aren't locked.
Which leaves issue #2381:
http://subversion.tigris.org/issues/show_bug.cgi?id=2381 "Cannot commit
multiple WC paths which lack a common parent directory"
(And issue #2563, which has been marked as a duplicate of this issue)
A feature/enhancement request which asks to make subversion capable of
committing to multiple working copies at once.
As far as I can tell nobody is currently working on this, but it's not
really hard to implement this properly now.
(There was a quick and dirty implementation some time ago, but the new wc
library makes it much easier to implement this properly)
> svn: E155004: Commit failed (details follow):
> svn: E155004: Are all targets part of the same working copy?
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
I don't like that final message in the error: A failed commit should just
release the locks properly.
Received on 2011-04-12 11:17:51 CEST