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

[John Arbash Meinel]

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


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

If you just want to do it from the test suite, you can do:

tree.set_parent_ids([tree.last_revision(), 'ghost-revision-id'])
tree.commit("commit with ghost")

Note, however, that bzr-svn is currently the only way to introduce a
ghost revision *and* to mark a file as last-modified in that revision. I
think there would be a way to inject it if you manually set the values
in an inventory and call Repo.add_inventory().

The issue is that bzr-svn is preserving the last-modified information
from the ghost that it isn't including in the ancestry. bzr itself, and
other converters don't ever do that.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAks6aP0ACgkQJdeBCYSNAAPsNACgv6MJ20QFZ4bp4rx5ikxH4oEp
mcYAn0YR+wc8Iyd/paf2Z8eI6MAH0T7s
=Svqq
-----END PGP SIGNATURE-----