<br>Hi Robert, I have some real bzrlog data now.<br><br>As described, we were running bzr 1.17 when the original problem occurred. Following your suggestion, and after making backups of the affected repo, I took us to bzr 1.18. We ran 'bzr check' on the repo both before and after instralling bzr 1.18. The 'bzr check' using bzr 1.17 reported no problems. After installing bzr 1.18, 'bzr check' reported 91 "Missing inventory" messages. 91 is an interestingnumber, because it is also the number of revisions in the branch.<br>
<br>I am attching the bzrlog output showing two checks -- the first with bzr 1.17 and the second with bzr 1.18. I have made string substitutions to redact user and domain names, withotu affecting the meaning of the results.<br>
<br>I am interested to learn what these results mean if you have time to offer an interpretation.<br><br>Thanks,<br>~M<br><br><br><br><br><div class="gmail_quote">On Tue, Sep 1, 2009 at 2:32 PM, Maritza Mendez <span dir="ltr"><<a href="mailto:martitzam@gmail.com">martitzam@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Sun, Aug 30, 2009 at 7:14 PM, Robert Collins <span dir="ltr"><<a href="mailto:robertc@robertcollins.net" target="_blank">robertc@robertcollins.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Please try bzr 1.18; a number of bugs that can cause that were fixed in<br>
1.18, as well as local dirstate corruption that can occur.<br>
<br>
And, as this happened with 1.17, your coworker should run 'bzr check<br>
--tree' before doing further work in that tree.<br>
<br>
-Rob<br>
</blockquote></div><br><br></div></div>Thanks, Robert. I forgot to mention that I did have him run 'bzr check' and everything was fine. So this is really about understanding what happened and why it is (or is not) scary. We were planning to hold off upgrading until 2.0 settles down, but we might make the move to 1.18 because I believe all the work you did recently on dirstate can only help.<br>
<br>Thanks!<br><font color="#888888">~M<br><br></font></blockquote><div><br><br> </div></div>