The continuing repository-collision saga

Aaron Bentley aaron at aaronbentley.com
Thu Mar 26 13:25:32 GMT 2009


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

Ben Finney wrote:
> But I've taken explicit steps to ensure that I'm *not* using a
> rich-root repository for this branch. The repository is definitely not
> rich-root:
> 
> =====
> $ bzr info $HOME/Projects/debian/openoffice.org/
> Shared repository with trees (format: pack-0.92)
> Location:
>   shared repository: /home/bignose/Projects/debian/openoffice.org
> =====
> 
> The branch was created in that repository. I don't quite understand
> the info output:
> 
> =====
> $ cd $HOME/Projects/debian/openoffice.org/debian.devel/
> $ bzr info
> Repository tree (format: unnamed)
> Location:
>   shared repository: /home/bignose/Projects/debian/openoffice.org
>   repository branch: .
> 
> Related branches:
>   parent branch: /home/bignose/Projects/debian/openoffice.org/debian.unstable
>   submit branch: http://bzr.debian.org/pkg-openoffice/packages/openofficeorg/3.0.1/unstable/
> =====
> 
> What's going on here?

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

> When I sent Rene a previous patch bundle using
> Bazaar 1.5, it applied cleanly against Rene's repository. The only
> difference AFAICT is that I'm now using Bazaar 1.13rc1. I have *not*
> changed the repository or branch formats in between.

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.

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

iEYEARECAAYFAknLgkkACgkQ0F+nu1YWqI2oUACeISnii1RRkfZIiT2V5PKAIY9d
s5AAnjVlk47HfvUOc49EOFh5VVgNEIXT
=yqBJ
-----END PGP SIGNATURE-----



More information about the bazaar mailing list