Comment 4 for bug 655371

Problem is that my machine crashed, yes, and since I have ext4, the data was
not flushed, files were emtpy. As I understand it, these are index files,
can't they, somehow, be regenerated again when empty / missing / corrupted ?

Cheers

Sven

On Wed, Oct 6, 2010 at 1:01 AM, Martin Pool <email address hidden> wrote:

> *** This bug is a duplicate of bug 655503 ***
> https://bugs.launchpad.net/bugs/655503
>
> Hi Sven,
>
> This means one of the bzr repository files has been truncated to 0
> bytes. This typically happens because of a machine crash or filesystem
> error beyond bzr's control.
>
> To fix this you should be able to:
> 1- make a backup of the whole repository
> 2- move the c11dbecfe3a92f616a9be65a0f2b099f pack and index files out of
> the repository
> 3- run 'bzr pack'
>
> I also filed bug 655503 for this.
>
> ** This bug has been marked a duplicate of bug 655503
> need automatic recovery from truncated pack/index files
> * You can subscribe to bug 655503 by following this link:
> https://bugs.edge.launchpad.net/bzr/+bug/655503/+subscribe
>
> --
> bzr crashes on pull
> https://bugs.launchpad.net/bugs/655371
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Version Control System: New
>
> Bug description:
> bzr pull ../path from a sister repository caused bzr to crash. pulling
> again works normally.. This crash happens every so often without leaving any
> problems..
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/bzr/+bug/655371/+subscribe
>