RE: Bug with missing scheduled-for-delete dir

> It has *never* been correct to delete or move Subversion's
> version-controlled files without using a Subversion client. I hope a
> future wc rewrite relaxes that, but for now, that's the breaks.

I hope that too. I am disappointed in the "that's the breaks" attitude.

>> It seems trivial to remove the scheduled-for-deletion flag and just
mark
>> it as missing.
> That seems wrong. If you said "svn rm foo" and haven't committed it
> yet or done a revert, why should it stop being scheduled for deletion?

Upon further thought I agree, missing would not be accurate.
 
As far as I can tell there are multiple bugs here:

1. status shows 'D' without -u and '!' with -u.
FIX: They both should show the same thing, though -u might show '*'.

2. status on the missing path fails with a completely screwy message.
FIX: I have no idea, something is very wrong here. 'afile' is in the
wc_root, but is reported as dir/afile.

3. update on the missing path fails uselessly depending on the contents
of the parent.
FIX: Why does it matter if the wc_root has a locked file or not?
Something is very messed up here.

4. revert fails with "Failed to revert 'wc/dir' -- try updating
instead."
FIX: Actually this is probably fine, as long as update worked.

I provided such a nice little recipe - can no one run a quick check
using a 1.5 client?

Thanks,

Eric

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-09 21:22:03 CET