This bug appears to be caused by the fact that this repository's uuid was changed. The old uuid appears to be 6d150e1c-e21c-0410-8b89-9ee68aed362b, while the new one is c3c08832-fc22-4c88-9867-b2b84583e700.
bzr-svn had references to the old revisions in some places, and is obviously no longer able to find the revisions with the old uuid. I think the sanest solution would be for bzr-svn to record what repository uuid a revision was created in, and check that when interpreting bzr metadata later. If the uuid set in the bzr-svn properties is different from the actual uuid, it would ignore the bzr revision id that was stored (but just that, it could still interpret the other bzr-svn metadata). -- Jelmer Vernooij <jel...@debian.org> - Jabber: jel...@jabber.fsfe.org
signature.asc
Description: This is a digitally signed message part
