'baz-import-branch' succeeds, but resulting branch is b0rked

Ben Finney bignose+hates-spam at benfinney.id.au
Wed Nov 8 02:46:30 GMT 2006


"James Henstridge" <james at jamesh.id.au> writes:

> On 03/11/06, Ben Finney <ben at benfinney.id.au> wrote:
> > What can I do to find out why this successfully-imported branch is
> > failing? Obviously, I also want to be able to use it with bzr.
>
> It is possible that something is failing due to the ghosts left behind
> by the import.

I'm not really sure why there would be ghosts.

> Assuming you've still got your benf at cyber.com.au--jobs-2005 archive
> around, try running baz-import-branch on the its-reporting--temp--0.2
> branch, and then use fetch-ghosts to bring that history into your
> converted branch.

It turns out the branch it was complaining about *did* still
exist. After 'bzr baz-import-branch' and 'bzr fetch-ghosts', bzr tells
me there are still a few dozen branches it needs revisions
from. Investigation shows they all still exist, and baz knows about
them.

What's causing 'bzr baz-import-branch' to miss the availability of
those branches?

> If you're switching over to bzr and have all the old history
> available, you should try and fill in all the ghosts so you have a
> full picture of the history.

How can I tell bzr to do that? Is there no alternative but to
'baz-import-branch' the *whole* history of *each* branch, just to get
the few dozen revisions I need scattered between them?

-- 
 \      "I stayed up all night playing poker with tarot cards. I got a |
  `\               full house and four people died."  -- Steven Wright |
_o__)                                                                  |
Ben Finney





More information about the bazaar mailing list