Comment 1 for bug 594155

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Szakmeister wrote:
> Public bug reported:
>
> We've set up a smart server instance using WSGI so that we could place
> access controls on the project branches. We really like to use a
> checkout of the server's branch to make merging into the mainline
> easier. Unfortunately, 'bzr co' attempts to acces .bzr/branch/branch-
> format instead of going through the smart server. Since we don't allow
> raw access to the branches, this fails. It should really be using the
> smart server transport. Interestingly, 'bzr branch --bind' works fine.
>
> Sorry I can't give you a short way to reproduce this, but I'd be happy
> to try a patch.
>
> ** Affects: bzr
> Importance: Undecided
> Status: New
>
> ** Summary changed:

There is often a difference between:

 bzr co bzr+http://
and
 bzr co http://

Did you try both?

The former requires all requests to go through the bzr protocol, the
latter allows access to certain requests to go via standard http. (For
stuff like reading the format files, is the most obvious difference.)

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwWltwACgkQJdeBCYSNAAOBgACfSJwI2YgdZ5qGkLcaP4KNzw/x
fj8An0Ykj9uYiy1LHSt9lBPZ9R8cdvs6
=8NBN
-----END PGP SIGNATURE-----