operations on broken repository give really ugly traceback

[Alexander Belchenko]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Today I have HDD failure when I pull patch to branch inside
the shared repository. After I restore access to HDD I see that
failure occurs when writing to inventory.knit or something similar.

Any operation on repository or working tree give me ugly traceback
(see attachment).

Primary goal of this message is not to ask help but point to this situation.
Even when I run `bzr check' I have the same ugly traceback.
I think that check command should be more robust against repository
corruption.

And yes -- in the future we need to have ability to automatically
or semi-manually restore broken repository after `check':
either from archives or from external reference repository.

What `bzr reconcile' does? Is this command help me to repair my repository?


Alexander

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFkPjezYr338mxwCURAuAvAKCKen08o9vg5GbYozx4APQh7gFMAQCfS2Tg
5wacQzYLof6IeeQIzVvzqA4=
=Rqiv
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: broken-repo.log
Url: https://lists.ubuntu.com/archives/bazaar/attachments/20061226/13d6a212/attachment.diff