Rob McBroom wrote:
On Sep 14, 2007, at 10:27 AM, Constantinos Neophytou ♎ wrote:
aha... even though svn -u st reports that everything is up to date, the diff -ru command shows that, in fact, everything is out of date (according to the metadata). The 'old' sandbox started as a checkout of version 5, and for some reason after the commit the metadata did not get updated, and refuses to get updated. It could not be permission problems, but i tried everything with sudo anyway, and I get the same errors...
Is your working copy checked out to a local HFS+ file system or is it stored remotely and accessed via AFP, Samba, SSHFS, etc?
IIRC, when the svn client updates metadata in the working copy, it does some sort of locking that most remote filesystems don't support.
Yep, I get someting like this when using Tortoise in the Parallels VM on a shared working copy. Any commit fails afterwards My error is clearer though: it says it can't move one of the .svn/ files, usually .snv/entries. This happens because svn sets the no-change flag in HFS. I solve it with
chflags -R noucgh working_copy/
You should normally get a permission error when something like this happens though. Cheers, V.-