'bzr blame' fails with ghost revisions and 'bzr check' output...

[John Szakmeister]

On Tue, Dec 29, 2009 at 2:24 PM, John Szakmeister <john at szakmeister.net> wrote:
> One of the members on my team ran across an issue when running blame
> with ghost revisions (and it looks like there is an open ticket about
> running 'bzr diff' when one of the revs is a ghost too).  I reproduced
> the issue, and ran 'bzr check' against the new branch (one with a
> ghost rev in it).  I'm not sure I understand the output:
>    Checking working tree at '/Users/jszakmeister/projects/tmp/new-trunk'.
>    Checking branch at 'file:///Users/jszakmeister/projects/tmp/new-trunk/'.
>    Checking repository at 'file:///Users/jszakmeister/projects/tmp/new-trunk/'.
>    checked repository <bzrlib.transport.local.LocalTransport
> url=file:///Users/jszakmeister/projects/tmp/new-trunk/> format
> <RepositoryFormat2a>
>         4 revisions
>         2 file-ids
>         1 ghost revisions
>         1 inconsistent parents
>    checked branch file:///Users/jszakmeister/projects/tmp/new-trunk/
> format Branch format 7
>
> I'm a bit confused about the inconsistent parents line.  What does
> that mean?  There's nothing in the help that mentions this... but it
> seems bad.  Can someone please explain what it means?

...and one more thing: anyone know how to create a repo that has ghost
revisions without something like bzr-svn?  I'd like to add a failing
test to the test suite, but I haven't a clue how to make this happen.

Thanks again!

-John