Below is a script that shows checking in a file which can not be
checked out. The scenario is 2 files, 1 is a symlink to the other,
the symlink is an executable (svn:executable is set), and it comes
first in the directory listing used by svn (alphabetical?). I am
using subversion 1.4.3.
This is bad enough, but I have yet to figure out how to remedy the
situation. I thought to propdel the property, but svn propdel won't
work on a non-local (url) argument, and of course I can't check the
file out.
This is just a test case to reproduce the bug, but in our actual
repository where this happened, a directory containing this mix-up was
subsequent svn copy'd to trunk. The resultant copy is reported as
"unknown node kind".
Any advice welcome!
Thanks
Kylo
---------------
#!/bin/bash
PWD=`pwd`
echo
echo "*** creating repository with 2 files, a and bar, a is a symlink to bar"
svnadmin create testrepo
svn co file://$PWD/testrepo wc
cd wc
touch bar
ln -s bar a
svn add a bar
svn ci -m ""
cd ..
rm -rf wc
echo
echo "*** checkout works"
svn co file://$PWD/testrepo wc
echo
echo "*** setting executable prop on the symlink"
cd wc
svn ps svn:executable ON a
svn ci -m ""
cd ..
rm -rf wc
echo
echo "*** now checkout doesn't work"
svn co file://$PWD/testrepo wc
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Mar 24 02:23:58 2007