> -----Original Message-----
> From: C. Michael Pilato [mailto:cmpilato_at_collab.net]
> Sent: woensdag 9 juli 2008 1:22
> To: Bert Huijben (TCG)
> Cc: dev_at_subversion.tigris.org
> Subject: Re: Can't commit multiple externals with depth infinity
>
> Bert, this is almost certainly caused by the fact that your current
> working
> directory and your externals directories are disjoint.
My current directory is the directory containing the externals
> In non-recursive commit mode, though, Subversion is more conservative
> about
> its locking, which turns out well in your case, as it never bothers to
> check
> for each locked target that they all live in a single working copy.
Can I (and can TortoiseSVN+AnkhSVN) depend on this 'feature' for future 1.X versions of subversion?
I just played a little further and came to an even stranger svn error.
> > Using subversion 1.5.0:
> >
> > ============================
> > # Create a test repository
> >
> > svnadmin create e:/q/repos
> > svn mkdir -m "" file:///e:/q/repos/root
> > svn mkdir -m "" file:///e:/q/repos/a
> > svn mkdir -m "" file:///e:/q/repos/b
> >
> > # Create working copy
> >
> > svn co file:///e:/q/repos/root wc
> > pushd wc
> > svn pe svn:externals .
> >
> > # Add this to the externals property
> > # a ^/a
> > # b ^/b
> >
> > # Then fetch the externals
> > svn up .
> >
> > # Make a few more changes
> > echo > a/file
> > echo > /b/file
> > svn add a/file b/file
> >
> > # This fails:
> >
> > svn ci . a/file b/file -m ""
> > #svn: Are all the targets part of the same working copy?
> > #svn: Unable to lock 'E:\q\root\a'
> >
> > # But this succeeds:
> > svn ci --depth=empty . a/file b/file -m ""
> > #Adding a\file
> > #Adding b\file
> > #Sending .
> > #Transmitting file data ..
> > #Committed revision 4.
svn pe .
# Add the following external to the two existing externals
# http://svn.collab.net/repos/svn/trunk/build/ build
svn up
echo > a/f
echo > b/f
echo > build/f
# And then as expected
svn ci -m "" . a/f b/f build/f
#svn: Are all the targets part of the same working copy?
#svn: Unable to lock 'E:\q\root\a'
# But then I tried
svn ci -m "" a/f b/f build/f
#svn: Commit failed (details follow):
#svn: Unrecognized URL scheme for ''
============================
I never would have guessed this error.
Bert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-07-09 01:42:35 CEST