Comment 3 for bug 598174

On Thu, 2010-06-24 at 18:37 +0000, Brian de Alwis wrote:
> I remembered that I still had the original repository. Experimenting
> some more, I've found how to reproduce the problem:
>
> 1. bzr branch git://github.com/sonatype/sonatype-tycho.git tycho-trunk
> 2. bzr branch -r git:e3496cbba2628c05a8d03d6a95af026dab1d3fa2 tycho-trunk tycho-past
> 3. cd tycho-past
> 4. bzr colo-ify
> Note that 'bzr git-objects' runs fine (when run from .bzr.branches, the repository).
> 5. bzr pull git://github.com/sonatype/sonatype-tycho.git
>
> And the problem recurs if I "rm -rf .bzr/branches/.bzr/repository/git"
> and then repull.
Can you reproduce this without involving colo-ify ? If not then I expect
this to be an issue in bzr-colo somewhere.

colo-ify somehow seems to create a cache database for bzr-git or perhaps
creates ghosts.

The code path that causes this exception to be raised is only executed
based on information in the cache, and that cache should not exist yet
(since you have a vanilla branch, created by "bzr branch").

Cheers,

Jelmer