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

Re: Help with 'svn: 'XXXXXXXXX' has no ancestry information' type error

From: Jonathan Gold <dev_at_samizdatdigital.com>
Date: 2007-06-08 17:14:00 CEST

Steve --

Thanks for the tips. I'd tried that (and some variations) yesterday, but to no
avail. Your suggestions were helpful anyway, since it got me to try a few more

The ultimate culprit, it seems, was that there was also an svn checkout in an
ancestor directory to the one in which I was having problems, and that parent
and my current dir were having naming-conflict issues. Generally, a pretty
stupid thing to do.

Nevertheless, if anyone from the svn-dev team is reading these things, I'd lobby
for more documentation or information to go along with this otherwise cryptic


On Fri, Jun 08, 2007 at 07:46:32AM -0400, Steve Bakke wrote:
> On 6/7/07 1:47 PM, "Jonathan Gold" <dev@samizdatdigital.com> wrote:
> > Hi --
> >
> > I'm having problems where I (perhaps inadvisably) blew away an .svn directory
> > and now, no matter how fresh a start I try to take with my workspace, cannot
> > do
> > a commit, getting the error mentioned in the subject line.
> >
> > It seems there was some discussion two months ago about it here:
> >
> > http://svn.haxx.se/users/archive-2007-04/0039.shtml
> >
> > but there was no response (and unfortunately what seemed to work for that
> > author
> > does not work for me).
> >
> > There was also this thread in 2006:
> >
> > http://svn.haxx.se/users/archive-2006-08/0104.shtml
> >
> > but as far as I can tell there was no followup or resolution posted.
> >
> > I can't seem to understand what is happening or how to fix it. Can anyone
> > help?
> >
> > jon
> >
> We've had to deal with issues relating to a tool which is unaware of
> subversion and regularly deletes and re-creates directories that are under
> revision control. This causes them to become obstructed, so our script
> wrapper is set up to automatically fix up the metadata.
> Our solution is to do a fresh checkout off to the side and then replace the
> missing/corrupted .svn in the appropriate directory. The other method is to
> do a fresh checkout and then move the contents of your old working copy to
> the new one.
> Either way, you should be able to checkin once you are done with that.
> -steve

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 8 17:19:34 2007

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.