[SVN-646] When svn:keywords changes, the local working copy doesn't

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: all
• Fix Version/s: M12
• Component/s: src
• Assignee: Unassigned
• Reporter: Subversion Importer
• Created: 11/Mar/02 22:30
• Updated: 27/Oct/18 16:42
• Resolved: 15/Sep/04 08:43

Description

When a change is made to a file's svn:keywords property (to add a new keyword,
for example), and the change is committed to the repository, the working copy
doesn't update until you force an update of the file (easily done by 'rm
<file>;svn up' or any kind of modification requiring a check-in).

The URL contains a quick test script to demonstrate the problem. Here's the
output from it:

+ svnadmin create repos
+ mkdir test
+ cd test
+ echo 'testing!'
+ echo '$LastChangedRevision$'
+ svn import file:///home/esm/test/repos/ . test
Adding          ./test
Adding          ./test/testfile
Transmitting file data .
Committed revision 1.
+ cd ..
+ rm -rf test
+ svn co file:///home/esm/test/repos/test/
A  test/testfile
+ cd test
+ cat testfile
testing!
$LastChangedRevision$
+ svn propset svn:keywords LastChangedRevision testfile
property `svn:keywords' set  on 'testfile'
+ svn commit -m 'Added $LastChangedRevision$ keyword.'
Sending         /home/esm/test/test/testfile

Committed revision 2.
+ cat testfile
testing!
$LastChangedRevision$
+ rm testfile
+ svn update
Restored ./testfile
+ cat testfile
testing!
$LastChangedRevision: 2 $

http://esm.logic.net/projects/svn/property-problem/

Original issue reported by emarshal