bzr serve and access control?

Josef Wolf jw at raven.inka.de
Wed Feb 3 06:42:39 GMT 2010


On Tue, Feb 02, 2010 at 08:30:48PM -0500, Gordon Tyler wrote:
> -----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.

I am new to bzr and don't yet understand the details here. But it looks
strange to me that it needs access to my /bin, /sbin, /etc and whatever...



More information about the bazaar mailing list