Unexpected property when replacing file in wc (svn 1.4.3)
From: Bernd <rbernd_at_gmail.com>
Date: 2007-03-25 15:57:27 CEST
Hi,
when replacing a file in the working copy and then adding a new property (all within the same transaction), a property set on the replaced file is still set. If, on the other hand, the file is replaced in one transaction and the new property is set in another transaction, the property of the replaced file will be gone (as I would it to be in both cases). This seems to be a bug or at least quite unexpected behavior.
Note that when committing the replaced file first and then setting a new property, the behavior is different (and as I would expect) in that only the new property is set.
svn, version 1.4.3 (r23084)
Recipe:
---- #! /bin/sh DIR=`pwd`/ttt if [ -e $DIR ]; then echo "$DIR exists" exit 1 fi mkdir $DIR cd ttt svnadmin create repos REPOS_DIR=$DIR/repos svn co file://$REPOS_DIR wc echo "test" > wc/file svn add --no-auto-props wc/file svn ps "prop1" "true" wc/file svn ci -m "" wc svn up wc svn rm wc/file echo "test" > wc/file svn add --no-auto-props wc/file # Uncomment the following line to make prop1 go away #svn ci -m "" wc svn ps "prop2" "true" wc/file svn ci -m "" wc svn pl wc/file # Output is: #Properties on 'wc/file': # prop1 # prop2 # Would expect: #Properties on 'wc/file': # prop2 cd .. rm -fR $DIR ---- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org For additional commands, e-mail: dev-help@subversion.tigris.orgReceived on Tue Mar 27 00:18:20 2007 |
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.