svn thinks a file is not modified, but it is!

[Mikel Ward <mi...@mikelward.com>]

Hi

I'm using svn 1.4.6 (r28251) on Fedora 9 preview (Linux i686) with an
svn+ssh repository.  As far as I can tell, the repo is running 1.4.2
(r22196).

I tried to commit a file yesterday, but it failed for some reason.  It
left an svn-commit.tmp file.  I think the reason was "working copy out
of date" or similar, but I also often abort checkins manually.

The repository definitely doesn't have the change (doing a fresh
checkout shows the old contents), but my working copy obviously got
corrupted, because svn stat, svn di, and svn ci all do nothing.
.svn/text-base contains the changes (I assume it would be the same
inode as the working copy, except I copied the working file to a
backup name then copied the backup over the working copy to see what
would happen).

Please let me know if there's anything I can do to help figure out the problem.

Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org