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

My repository is buggered?

From: Colleen Dick <platypus_at_peak.org>
Date: 2006-06-04 08:04:10 CEST

We can't commit this one critical file.
All our development is at a standstill until we can get this fixed.

Everything was humming along quite nicely until I tried a commit this
morning and I got a checksum failure on this one file. So I tried some

When I did svn log on this file, the last time the repository thought I
made any changes to this file was rev 366, but
locally the entries file said that the last version where I changed that
file was 379. (I'm now on about 403 or so) No problem I'll just:
1) check out the problem directroy version 366,
2) hack the entries block from it into the one in my working copy,
3) hack the 366 text-base version into my working copy text-base,
4) copy version 366 into the working copy and manually apply the diff
from the latest version No problem. OK, the working copy is working
locally time to commit.

Now I'm getting this
Transmitting file data ...svn: Commit failed (details follow):
svn: Out of date: '/trunk/classes/class.Event.php' in transaction
svn: Your commit message was left in a temporary file:
svn: '/var/www/html/tixrus/svn-commit.6.tmp'

Is there some date I need to tweak?

Now here's the scary part: I just did another svn log on that same file
class.Event.php Previously the log for this file started at rev 366 and
worked its way backwords. Now the log is claiming the last change to
this file is rev 66 which was MONTHS AGO!!!

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jun 4 08:11:54 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.