The continuing repository-collision saga

[Aaron Bentley]

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

Ben Finney wrote:
> Aaron Bentley <aaron at aaronbentley.com> writes:
> 
>> Not sure. The "format: unnamed" bit means you've got a
>> tree/branch/repository format combination that can't be requested
>> via "bzr init". My guess is you have a Branch5 branch. What's the
>> output of "bzr info -v"?
> 
>         branch: Loom branch format 6

Ah, yes.  You can't request a loom branch from init, either.

>> If you'll send me the bundle, I can have a look. Please be sure to
>> send the original bundle-- don't re-run bzr send.
> 
> Shall do, in a separate message.

This is pretty mysterious.  As far as I can tell, the bundle does not
use rich roots.

Its initial info field says
d10:serializer1:512:storage_kind6:header18:supports_rich_rooti0eeB135

(the i0 means false)

The inventory serializer used is format 5, which again does not support
rich roots.

It's possible bzr tried to retrieve missing revisions from the target
branch, which you have set to
'../debian.unstable/'

If that's a rich-root repository, that might have caused problems like this.

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

iEYEARECAAYFAknLjBsACgkQ0F+nu1YWqI2mXgCcCeWPJYycfj2CXbiwueEEWQB0
WK0AoILsjyNehf11lEg+0unFd4t9zgQz
=Tpc2
-----END PGP SIGNATURE-----