permissions problems on sftp repo [SOLVED]

Thomas Nichols nichols7 at
Mon Mar 10 16:44:15 GMT 2008

John Arbash Meinel wrote on 2008/03/10 14:21:
> Thomas Nichols wrote:
> | So now my question is: why is this not the default action of bzr init?
> ... snip ...
> I'm not sure that it would help a lot. Specifically, a lot of systems 
> default to
> creating files as something like "jameinel.jameinel" (they create a group
> account matching the username and set it as the default group). So at 
> that point
> setgid doesn't help, you need to chown anyway, which means you need to 
> know
> enough about chown and chmod. (Plus many default to a umask of 0022 so 
> the group
> doesn't have write access anyway.)
> John
> =:->

All true - perhaps it is worth adding a `bzr` group as part of a default 
bzr install, and having bzr init create .bzr as `drwxrws--- 
someuser:bzr` ? Then the instructions are pretty simple for end users:

 To access this repository over ssh, use  
bzr+ssh://user@host/path/to/repo. Every user writing to the directory 
should belong to the `bzr` group on the server, and the repository 
should allow write access to the group:
    gpasswd -a funkyuser bzr
    chmod -R g+w .bzr

Anyone wanting to run more than one repo, with different groups, is 
still going to have to do some reading; but they probably only need
    chgrp -R funkygroup .bzr
which seems rather easier to grok than the setgid/setuid/sticky-bit 
malarkey. For most bzr+ssh users, might this make life rather simpler?

Not a big deal so long as the `chmod -R g+s .bzr` solution is documented 
somewhere -- did I miss it? Or should I write some text for that?

-- Thomas.

More information about the bazaar mailing list