bzr serve and access control?

Gordon Tyler gordon at doxxx.net
Wed Feb 3 01:30:48 GMT 2010


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

On 2/2/2010 6:31 PM, Josef Wolf wrote:
>> Then the server would refuse access to the 'repository'. The client does
>> not know *where* the repository is until we've connected. (As it could
>> have been in /srv/repo, or /srv/repo/a_project or
>> /srv/repo/a_project/branch.)
> 
> How comes that the client doesn't know where the repos is located although
> I have passed this information on the command line?
> 
> If you say "bzr branch bzr+ssh://host/srv/repo/a_project/branch" (as in
> your example above), it looks pretty much as you are trying to access
> /svn/repo/a_project/branch on "host". How comes that bzr client is not able
> to know that? How can it retrieve the data when it doesn't know where to
> get it from?

The path that you give to bzr is the location of the *branch* and not
the *repository*. bzr needs access to both. However, it cannot locate
the repository until it reads the branch data (which contains a pointer
to the repository) and to read the branch data it needs to start the
'bzr serve' process.

Ciao,
Gordon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLaNHIAAoJEIrPJfWinA2ut4AH/AjYKRgjinKdxSW6inNAGkj4
RClSvT1HJATT2ZCQIhuS5S4Hou+l1MVPtZNbfLPGpUJJJ9A4vLbk6cpjflL2DaMZ
aDB7aRgG5nE91OFlKbk+l4DCdwSi6wEEXLI3PsG14MHFG+E6mL6+OyoEmYvuEOo4
127LkncuKS6lGHlvD8GK0tbirUUugdwD0a/fcK1fB1YEtBd0FT/gMU5gyEnlgKI6
ZXwwgy0y88pGSZ3OgRb5/inpeBwzy3J8xLUbkawqhl2KUAPU5CTnxtvODJyqA74L
O0Lgq9UZ0KzDtb8MHfDXR1FpqInK5MzAaWVlVsteEncKuGvN3LVmIl8CYYJXXFw=
=iZPj
-----END PGP SIGNATURE-----



More information about the bazaar mailing list