<div class="gmail_quote">On Thu, Sep 30, 2010 at 4:47 PM, Martin Pool <<a href="mailto:mbp@canonical.com">mbp@canonical.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div class="im">On 30 September 2010 10:17, Philip Peitsch <<a href="mailto:philip.peitsch@gmail.com">philip.peitsch@gmail.com</a>> wrote: > Hi Everyone, > > Just a quick warning that if you are using bzr-svn, updating from 2.2.0 to > 2.2.1 may not be as safe as I first hoped. At least 5 of the devs I work > with have found their local repositories now suffer from > <a href="https://bugs.launchpad.net/bzr/+bug/485601" target="_blank">https://bugs.launchpad.net/bzr/+bug/485601</a> when attempting to check files > into a remote repository running bzr 2.1.1. Note this may not affect > "normal" bazaar workflows, as we make heavy use of bzr-svn, and most of our > synchronization happens via an svn trunk, rather than peer-to-peer bazaar > sync'ing. </div>Hi, thanks for the heads up. Just to be clear, you're saying the bzr+ssh server was running 2.1.1 the whole time, and the clients upgraded from 2.2.0 to 2.2.1? </blockquote><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> -- Martin </blockquote></div> The server itself is running debian lenny, with bzr 2.1.1 manually installed. All the clients are running via bzr+ssh on Windows boxes (both XP & 7). We are running a mix of 2.1.1, 2.1.2 & 2.2.0 depending on how adventurous the particular dev is :). I'm working with the dev's at the moment to get all local copies of the repositories deleted, as we have a network shared repo they all use as well which I will be running the reconcile --canonical-chk business on tonight. I thought it'd be gratifying for you guys to hear that in spite of this hick-up (our second major one in two months... the last one was caused by another bug), the devs are still pretty keen on continuing on with bazaar if I can get things repaired. I thought that after a second local repo loss a few users might be a little gun-shy, but most still feel the pro's far outweigh the con's... so congrats to all you devs for the powerful tool you've built! -- Philip Peitsch Mob: 0439 810 260