The continuing repository-collision saga

Aaron Bentley aaron at aaronbentley.com
Fri Mar 27 14:40:15 GMT 2009


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

Ben Finney wrote:
> Aaron Bentley <aaron at aaronbentley.com> writes:
> 
>> 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.
> 
> I hope that's not a problem.

It's not a problem.  It's just why the format is unnamed.

>> 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.
> 
> It isn't (also, Rene would not have it by that name, so I can only
> interpret you as meaning that *my* Bazaar client tried to retrieve
> From it when creating the bundle).

I mean Rene's client.

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

iEYEARECAAYFAknM5UwACgkQ0F+nu1YWqI2ScgCdHm0Q0zQo2Bg8ZgTCX70UUIJe
TFkAmwTiKh5rFwk+doMQ+6azhO04qRO3
=QQbp
-----END PGP SIGNATURE-----



More information about the bazaar mailing list