[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Mikel Ward <mikel_at_mikelward.com>
Date: Tue, 13 May 2008 16:10:27 +1000


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

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.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-13 21:35:02 CEST

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.