exceptions.ValueError: We are missing inventories for revisions

[Frits Jalvingh]

I get this while pulling an existing branch which was used without problems for a long time.

Branching again in the same shared repository causes the same error, appearently the shared repo has some problem.

The console output is:
jal@odeon:~/bzr/vp-split-execom$ bzr branch bzr://bzr/vp-trunk vp
bzr: ERROR: exceptions.ValueError: We are missing inventories for revisions: [('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',), ('<email address hidden>',)]

*** Bazaar has encountered an internal error. This probably indicates a
    bug in Bazaar. You can help us fix it by filing a bug report at
        https://bugs.launchpad.net/bzr/+filebug
    attaching the crash file
        /home/jal/.cache/crash/bzr-20091203073826-8410.crash
    and including a description of the problem.

    The crash file is plain text and you can inspect or edit it to remove
    private information.

[John A Meinel (jameinel)]

I believe this is a dupe, but I don't have the bug number off hand.

The issue is that bzr is trying to do an autopack, but some of the inventory pages are in a different set of pack files than the ones which are being combined.

If you just run "bzr pack" manually in that directory, it will get you back into a working state.

[Frits Jalvingh (fjalvingh)]

bzr check found no errors but the problem persisted after it. I then did a bzr pack; after that the problem was gone.

[GuilhemBichot (guilhem-bichot)]

we hit this one in our main repository. "bzr pack" fixed it.