Networking bugs in bzr 1.13/1.14

[Alexander Belchenko]

Robert Collins пишет:
> Bazaar 1.13 introduced streaming fetch over the bzr:// protocol, which
> makes push and pull operations substantially faster.  Unfortunately
> due to mismatches with existing code this does not operate correctly
> on stacked branches in many cases.  The server is unable to correctly
> determine the deltas to send and gives an error when you next try to
> pull from an affected branch.
> 
> If you are not using stacked branches this does not affect you.
> Bazaar will not create stacked branches by default unless you specify
> the --stacked option to push/branch, or set a server-side policy for
> them. Launchpad sets a server-side policy for stacking - users of
> Launchpad will be using stacked branches. You can tell if a branch is
> stacked by running 'bzr info BRANCHURL' and looking for
>    stacked on: URL
> in the output.
> 
> If you are using stacked branches, then using bzr versions before
> 1.13.2, 1.14.2 or 1.14 and above may create repositories that cannot be
> streamed from.
> 
> A fix for this issue in included in bzr 1.15.
> 
> There is another potential failure mode that may affect projects using
> bzr-svn, or migrating from GNU Arch. If you encounter a 'Revision
> REVISIONID not present' error when branching, you may be suffering
> https://bugs.launchpad.net/bzr/+bug/368418. A fix for this was also
> included in 1.15.
> 
> 
> Resolving this issue
> --------------------
> 
> Existing branches which are affected require a script run on them to fix
> them. The script and instructions are in
> https://bugs.launchpad.net/launchpad-code/+bug/354036.

Just yesterday me, Vincent and Dima Vasiliev found that this script is 
not enough to fix the problem. This script sometimes unable to fix the 
problem for read-only access via bzr+ssh.

JFYI.