Re: Incorrect LastChangedRev in working copy after committing directory move + modified file in subdir

Vincent Lefevre <vincent-svn_at_vinc17.net> writes:

> Anyway the URL of every file should be updated, shouldn't it?
> At least there is an inconsistency, shown by the following script:

[...]

> The output ends with:
>
> + cat dir2/file
> $Header: file:///tmp/my-test-svn/svn/dir1/file 2 2012-07-04 11:57:43Z vlefevre $
> + svn cat file:///tmp/my-test-svn/svn/dir2/file_at_3
> $Header: file:///tmp/my-test-svn/svn/dir2/file 2 2012-07-04 11:57:43Z vlefevre $
>
> file:///tmp/my-test-svn/svn/dir1/file_at_2 exists but this isn't the
> real URL of the file.

That's a keyword expansion bug, a variation on issue 1975.

> file:///tmp/my-test-svn/svn/dir2/file_at_2 doesn't exist.
>
> IMHO, the most intuitive Header string should have
>
> file:///tmp/my-test-svn/svn/dir2/file 3

Where would the revision 3 come from? LastChangedRev is 2. That's what
Subversion's cheap copy means.

LastChangedRev is the only revision we have, apart from the "current"
revision see:
http://subversion.apache.org/faq.html#version-value-in-source

-- 
Cerified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download