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

Re: svn status issues when deleting a file

From: Hari Kodungallur <hkodungallur_at_gmail.com>
Date: 2007-06-01 07:21:42 CEST

[sending it again, copying the list this time]

On 5/31/07, Peter Herth <herth@peter-herth.de> wrote:
>
> Hi,
>
> I have come about an issue with svn status I wanted to share for
> discussion whether my interpretation is wrong or this actually could
> be considered as a bug. My goal is to find out the latest version of a
> file/directory in the repository. Which should be in theory the latest
> commited version of a file (so the second number svn status prints
> out, if your workarea is up to date).
>
> I have a directory under svn version control with some files in it:
>
> 110 67 herth Hallo.txt
> 110 110 herth asdf
> 110 110 herth .
> Status against revision: 110
>
> now I delete "asdf" and commit the change. Running svn status -u -v gives
> me:
>
> 110 67 herth Hallo.txt
> 110 110 herth .
> Status against revision: 111
>
> Here the problem starts to manifest. I modifyed "." but neither the
> last committed version number changes, nor is it shown as out of date.
>
> if I run svn up, it changes to:
> 111 67 herth Hallo.txt
> 111 111 herth .
> Status against revision: 111
>
> So now status clearly reports that "." changed its latest committed
> version number from 110 to 111, without giving a hint in status
> before, that it was not at that version. Of course, updating did not
> actually change my workarea, as the deleted file was already gone. In
> this sense, the workarea was not really out of date. But then the
> status should have shown "." at 111 directly after the commit and not
> only after updating.
> Comparing to the behaviour of file changes, this confirms it, if I
> edit Hallo.txt I get:
>
> M 111 67 herth Hallo.txt
> 111 111 herth .
> Status against revision: 111
>
> and committing it I get:
>
> 112 112 herth Hallo.txt
> 111 111 herth .
> Status against revision: 112
>
> Here, committing did bump the revision of the file, without a need for
> an update. So I think committing of the file deletion should have
> bumped the version of the directory too, or am I missing something?
>

That is the way it works. It is not a bug that you are seeing and it is not
restricted to delete. If you add a file under a directory or subdirectory,
and you will see the same behaviour. Basically, the directory is another
entity with in the system that is versioned. It has properties that you
add/update/delete etc. So when you commit an entity (after
add/delete/update), only that entity gets its revision updated.

regards,
-Hari Kodungallur
Received on Fri Jun 1 07:22:03 2007

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