On 22/12/2011, Gary Poster <gary.pos...@canonical.com> wrote: > Anyone (Aaron?) have any ideas on what we can do to help them?
See John's earlier investiagtion in this answer for a technical summary: <https://answers.launchpad.net/bzr/+question/175127#comment-4> Short version, there's nothing the leo-editor guys can do to fix their repository, the problem revision was uncommitted but is stuck in the base repository. When using bzr+ssh the server knows not to send this data, but the unauthenticated http access ends up fetching it all. The problem is there's no way of robustly removing data from a repository when stacking is involved, as it's hard to tell whether a particular revision is referenced by some branch somewhere. However, given the pain this has caused, I think the best thing to do is create a completely fresh, unstacked repo, branch leo-editor trunk into it, and replace the current repository with that, living with any breakage. I just have no ability to actually do this kind of thing for launchpad branches, nor enough about the underlying setup to walk a losa through the process. I hoped between us we could work out some kind of solution though. Thanks, Martin _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
