Comment 5 for bug 507040

Not sure about the dupe here but Nicola said that this repo is used by branches stacked on *another* repo.

So 'bzr check' may just be failing because it doesn't know about the other repo.

@Nicola, try to run 'bzr check' from a directory that set things up correctly, a stacked branch or a working tree
associated with a stacked branch.

But even there, if several branches (sharing that repo) are stacked onto *several* other repos, check can still crash
that way since it's supposed to check *all* revisions in the repository and some of them may refer to revisions
present in some stacked-on repos that check is not aware of....

If that's the case, I can see several ways to address the problem:
- scan all branches to collect all relevant repos before starting the check (urgh),
- add an option to check only the revisions appearing in the branch ancestry,
- if the error occur while checking a repo, output a warning about stacked branches ?

@Nicola: Can you tell us how you use that shared repo ?
Are all branches stacked onto the same external repo ?
If yes, does a 'bzr check' from one of the branches succeeds ?
If still yes, does it succeeds for all the branches ?