Comment 2 for bug 145812

I just did an upgrade which left my repository in a wonderfully messed up state.

Thinking (incorrectly) I knew how to repair this, I copied backup.bzr to .bzr immediately, and expected to continue on my merry way. I was quite mistaken. My repository remained broken, and I thought I had potentially erased or permanently lost the entire repository of history. spiv from IRC helped me to recover by simply *also* moving "repository.backup" to "repository" *within* the ".bzr" (what was my backup.bzr) directory. This is highly unintuitive and confusing, but much worse, it's not mentioned anywhere, leaving me to potentially ruin my repository without knowing it could still be salvaged.

I'm all for fixing the upgrade breakage, but could the error information provide detaild and safe steps to fix the repository as well? That would be very helpful.

-Chandler