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

Re: "svn move" broken?

From: Faheem Mitha <faheem_at_email.unc.edu>
Date: 2003-06-05 23:50:41 CEST

On 05 Jun 2003 08:21:14 -0500, Ben Collins-Sussman <sussman@collab.net> wrote:
> Michael Schmitt <schmitt@TI.Uni-Trier.DE> writes:
 
>> After all while, I found out what this message means and I ran "svn
>> update subdir1". And here comes the surprise:
>>
>> D subdir1/FileXXX1
>> D subdir1/FileXXX2
>> ...
>>
>> Although all previous commits were successful (at least I thought so),
>> svn did not update my working copy correctly! Or, more precisely, it
>> did not update the meta information in my working copy, since the real
>> files had definitely gone before! And there was no other user working
>> in this project at the same time.
>
> This is a buglet that I believe we're working on. Fortunately, your
> analysis of the problem was completely wrong. The metadata *was*
> tracked correctly in your working copy. The files were definitely
> gone already, and subdir1 definitely knew this information.
>
> The "D" actions you see were simply no-ops. The bug here is that
> subdir1 didn't correctly report its state to the server, so the server
> sent redundant commands that did nothing.
>
> Don't worry, this will be fixed.

This has been puzzling me too. I was going to post about this, but I
thought it likely due to my misunderstanding of how subversion
works. So, just to make sure I am understanding this correctly:

1) The deletes sent to the working copy were in fact redundant. So the
local .svn *was* fully up to date with respect to that. Once this
buglet has been fixed, no D messages will be sent on doing `svn up' in
a similar situation.

2) In that case, was the problem only that the revision numbers were
not synced up to the latest version across the entire directory
subdir1 (even though the files themselves in this case were up to
date), so it was just a matter of updating the revision numbers for
the files in the working copy of that directory (subdir1), and nothing
else? Since, as you said in another message to this thread:

 1. you cannot delete a file or directory which isn't at HEAD
    revision in your working copy.

                                                          Faheem.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 5 23:53:57 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.