<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style></style></head><body bgcolor=white lang=EN-CA link=blue vlink=purple><div class=WordSection1>Jelmer,<o:p></o:p><o:p> </o:p>I think I figured this out. I have some revisions in my Subversion repository which BOTH delete a node, AND create another node by copying from the node I’m deleting. In the same revision. I think Subversion’s flexibility is a detriment to me here. The svn log output for that revision follows:<o:p></o:p><o:p> </o:p>------------------------------------------------------------------------<o:p></o:p>r5152 | danm | 2009-05-29 10:57:09 -0600 (Fri, 29 May 2009) | 2 lines<o:p></o:p>Changed paths:<o:p></o:p> D /tng/mrld-p3e-activity-property-rollup-svc/branches/api6.2.1<o:p></o:p> A /tng/mrld-p3e-activity-property-rollup-svc/trunk (from /tng/mrld-p3e-activity-property-rollup-svc/branches/api6.2.1:5151)<o:p></o:p><o:p> </o:p>Repatriate api6.2.1 branch to trunk.<o:p></o:p>------------------------------------------------------------------------<o:p></o:p><o:p> </o:p>This is confusing bzr-svn. In theory I don’t think it should because the Node-copyfrom-rev is 5151, which is the revision before this one, and in that revision the node I’m copying from still exists. But I guess what I’m doing is kind of silly.<o:p></o:p><o:p> </o:p>The error is happening when I run bzr svn-import.<o:p></o:p><o:p> </o:p>I think I can fix this by doing svnadmin dump, hacking the dump file (in this case, probably by moving the delete operation into revision 5151 and changing Node-copyfrom-rev to 5150), re-creating my Subversion repository, and re-running the import. Or maybe it would be as simple as re-ordering the delete and add operations in the dump file.<o:p></o:p><o:p> </o:p>I’m doing a one-time conversion and I’m already following this general process to fix a few cases where sloppy use of Subversion breaks the ancestry of a project when it’s imported into Bazaar.<o:p></o:p><o:p> </o:p><div>Dan MacMillan | Integration Specialist Emerald Associates Inc. Direct: 403.686.7100 ext 8930 Toll Free: 1.877.316.6005 ext 8930<o:p></o:p><o:p> </o:p>Canada's Exclusive Oracle Primavera Platinum Partner<o:p></o:p></div><o:p> </o:p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>From: bazaar-bounces@lists.canonical.com [mailto:bazaar-bounces@lists.canonical.com] On Behalf Of Jelmer Vernooij Sent: Friday, March 23, 2012 16:21 To: bazaar@lists.canonical.com Subject: Re: Error running svn-import ... ghost in ancestry?<o:p></o:p></div></div><o:p> </o:p>Hi Dan, Am 22/03/12 17:49, schrieb Dan MacMillan: <o:p></o:p>I’m migrating some of our projects from Subversion into Bazaar and a couple of them show errors like this:<o:p></o:p> <o:p></o:p>bzr: ERROR: Could not determine revno for {svn-v4:f28f6c95-3c17-0410-b47b-f95b9e4a518a:tng/mrld-p3e-activity-property-rollup-svc/branches/api6.2.1:5152} because its ancestry shows a ghost at {svn-v4:f28f6c95-3c17-0410-b47b-f95b9e4a518a:tng/mrld-p3e-activity-property-rollup-svc/branches/api6.2.1:5152}<o:p></o:p> <o:p></o:p>I’m not sure how to interpret this. It seems to be saying it is its own ancestor? Am I reading that right?<o:p></o:p>It's mostly saying that it's trying to determine the revision number for a revision that is not actually present in the repository. When are you getting this error, exactly? Cheers, Jelmer<o:p></o:p></div></body></html>