branch: Repository KnitPackRepository is not compatible with repository KnitRepository

[Ben Finney]

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

> Your "Projects.BROKEN-REPO" repository supports subtrees, which can
> contain data that can't be represented in a pack-0.92 repository
> (whether the revisions in your repository make use of that or not is
> another question).

Curiosity compels me to ask: Why is a default 'init-repo' command in
Bazaar 1.3 creating a repository in a format ("pack-0.92") that cannot
contain data from a repository with subtrees (created with a version
of Bazaar around 1.0)? Shouldn't a *default* 'init-tree' be
backward-compatible with repositories created by older versions?

> I am not sure what the recommended upgrade path is for this case.

Am I wrong to expect that Bazaar should by default be allowing an
upgrade path from repositories created by older versions?

Regardless of the answer to that, or whether I will understand the
answer, all I actually want to know in this instance is how to move to
a non-broken repository that allows new branches by default and
preserves all my existing branches. I hope someone here can help me.

-- 
 \         "What is it that makes a complete stranger dive into an icy |
  `\     river to save a solid gold baby? Maybe we'll never know."  -- |
_o__)                                                      Jack Handey |
Ben Finney