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

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ben Finney wrote:
> "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.

Ghosts aren't supposed to be a problem.  The Bazaar history has ghosts,
for example.  And our plans for "shallow" branches rely on the fact that
ghosts are legal.  So it appears that fetch is broken.

You asked to import just the branch (rather than doing baz-import).  So
you got just the revisions in that branch, which is consistent with the
Arch model.

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

That is by design.  The other branches may be on the other end of slow
network connections, or unavailable, or corrupt.

> 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?

You shouldn't need them, and we should investigate why fetch is trying
to retrieve them.  But you can use "baz-import" to convert an entire
archive, and that will only convert each revision once.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFUVHW0F+nu1YWqI0RAjkMAJ44ozndLyAJDw95WnTBxoYwYDdvlQCeMtz4
RDvY3PsZuc53oSVUZ7UGUVI=
=9r2J
-----END PGP SIGNATURE-----