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

Re: missing revisions on checkout or update

From: Blair Zajac <blair_at_orcaware.com>
Date: Thu, 27 Mar 2008 10:46:22 -0700

Paul Koning wrote:
>>>>>> "John" == John Doe <ufnoise_at_gmail.com> writes:
> John> I'm having a very serious issue where if I do a checkout of my
> John> code to a new directory, I am getting an old revision which is
> John> missing several files and directories I had added. I spent
> John> some time worried since several hours of development were
> John> missing.
> John> I was able to locate a checkout on my machine at 229 having an
> John> important directory that was missing.
> John> If I do: svn co file:///path/to/my/project
> John> it lists the files and then states: Checked out revision 166.
> John> If I do:
> >> svn update -r head
> John> At revision 166.
> John> But if I do:
> >> svn update -r 229
> John> all of my missing files in my missing directory are now present
> John> and it states: Updated to revision 229.
> I see something like this also. Very strange.
> So don't do that. If you want to update to the latest, just say "svn
> update" without any -r argument.

Avoiding saying 'update -r' is not going to solve anything. If it thinks that
HEAD is 116 while you can update to 229, then something is broken.

I would run a verify on the repository, see if there's anything wrong with it.

You don't have multiple people using the same file:// repository, do you? If
you do, I suggest moving to using mod_dav_svn or svnserve, which is much better.


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-27 18:47:18 CET

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.