Re: Catching dangling transactions

Julian Foad <julianfoad@btopenworld.com> writes:

> Here it shows that a second attempt at an obstructed update leaves a
> dangling transaction:
>
> ~/tmp/svn-sandbox> svn up At revision 36. [No dangling transactions
> in '/home/julianfoad/vcs/sandbox']
>
> ~/tmp/svn-sandbox> svn up -r33 UU f
> /home/julianfoad/src/subversion/subversion/libsvn_wc/update_editor.c:798:
> (apr_err=155000) svn: Obstructed update svn: failed to delete file
> 'eol-test': file has local modifications. [No dangling transactions
> in '/home/julianfoad/vcs/sandbox']
>
> ~/tmp/svn-sandbox> svn up -r33
> /home/julianfoad/src/subversion/subversion/libsvn_wc/update_editor.c:798:
> (apr_err=155000) svn: Obstructed update svn: failed to delete file
> 'eol-test': file has local modifications. ### Dangling transactions
> in '/home/julianfoad/vcs/sandbox': 5c

Those two updates are not quite the same, after the first update fails
the working copy is marked incomplete. When I try it, all obstructed
updates in an incomplete working copy leave behind a transaction.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org