Missing referenced chk root keys

[Adrian Wilkins]

Ran into this whilst trying to merge a revision from my laptop.

Happily, my laptop merges the revision from my desktop without incident.

Unhappily, the desktop machine refuses to pull the branch from the laptop afterwards, or have it pushed from the laptop to the desktop.

The repository contains multiple branches that are branches of SVN branches, from multiple SVN repositories. These are peer-ed around between a server and three working machines. The branch in question was branched off the mirror branch and had revisions committed to it on two working machines in parallel.

[Adrian Wilkins (adrian-wilkins)]

Also tried pushing the branch to a new branch on the machine - which works ; and then branching it into the previous repository - which doesn't (same error).

[Adrian Wilkins (adrian-wilkins)]

`bzr check` on the affected repository reports no errors.

[Adrian Wilkins (adrian-wilkins)]

Tip of bzr.dev does not exhibit this problem, and has pulled the revision successfully.

[Jelmer Vernooij (jelmer)]

On Tue, 2009-09-29 at 23:00 +0000, Adrian Wilkins wrote:
> Tip of bzr.dev does not exhibit this problem, and has pulled the
> revision successfully.
Thanks for letting us know. I'll close this bug.

  status fixreleased

[Adrian Wilkins (adrian-wilkins)]

Reinstating this ; it just defers the problem until you try to do an update, then you have the error ;

bzr: ERROR: exceptions.ValueError: A request was made for key: ('sha1:2d3e0631c180d90eda84abae5273e1237e73cdd5',), but that content is not available, and the calling code does not handle if it is missing.

[Jelmer Vernooij (jelmer)]

Can you reproduce this with a fresh clone of a Subversion repository ?

[Adrian Wilkins (adrian-wilkins)]

I have a feeling this may have been down to disk corruption ; the different behaviour of 2.0 and bzr.dev probably distracted me from reaching that conclusion.