> (unassigning myself since you've managed to recover from this problem)
is extremely inaccurate---we have *not* managed to recover from this problem, since a "bzr branch" on this (very) public branch still causes bzr to fail. What is true is that there is a sequence of steps to take instead of a normal "bzr branch" that can allow the branch to be checked out, but we can hardly expect all users/developers to jump through these hoops.
In particular, this comment
> (unassigning myself since you've managed to recover from this problem)
is extremely inaccurate---we have *not* managed to recover from this problem, since a "bzr branch" on this (very) public branch still causes bzr to fail. What is true is that there is a sequence of steps to take instead of a normal "bzr branch" that can allow the branch to be checked out, but we can hardly expect all users/developers to jump through these hoops.