Hi,
I have noticed that if you don't have permissions on an unversioned
subdirectory of a working copy, and you go and svn add it, it causes
problems with the parent folder.
The exact effect is that the parent folder thinks that the subfolder is
added, but the subfolder doesn't have its ".svn" metadata.
This is a bit of an annoyance, as it confuses subversion.
A scenario which causes this:
User A has groups (UserA, Users) default UserA
User B has groups (UserB, Users) default UserB
User A:
mkdir project
chmod g+s project
chgrp Users project
svn co
http://repo/.. project
mkdir project/subfolder
chgrp UserA project/subfolder
User B:
svn add project/subfolder (fails, leaving "project" thinking subfolder
was added, and no "project/subfolder/.svn" metadata)
This is tested on Subversion 1.5.2, also I had this issue on Subversion
1.4.6
I found the only way to fix it after being done is for example:
chgrp Users project/subfolders
mv project/subfolder project/subfolder_tmp
svn revert project/subfolder
mv project/subfolder_tmp project/subfolder
It would be more ideal if subversion acted more atomically and would
rollback the add action on failure, as it has not fully completed.
--
Regards
Andrew Thompson
Fubra Limited
andrew@...
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
