Resolved - Re: Permissions on remote mercurial server

[Sean Kelley]

Created a 'mercurial' user on the server
Set up remote ssh access through public/private keys
Now all transactions handled through the mercurial user whose
authorized keys I update as new users are added.

Sean

On 6/10/07, Sean Kelley <svk.sweng at gmail.com> wrote:
> When I have a remote server and I am using ssh to create a new
> repository and then push my changes to it, how can I be assured that
> group permission with remain writable?
>
> For example, my user account on the remote server sets umask 002.  My
> local user likewise sets umask 002.  The remote directory that
> repositories are to be added has been set with chmod g+ws.  Yet, when
> I do the following:
>
> hg init ssh://hg.myserver.org//data/hg/sw/training
>
> The directory that is created  is drwx-r-s-r-x training
>
> If I am remotely logged into the server and I create a directory  it
> does have the correct permissions.
>
> I then do a push:
>
> hg push ssh://hg.myserver.org//data/hg/sw/training
>
> but the fact remains that the directory created and subsequent .hg
> folder are not group writable.
>
> Any suggestions on how I should be doing it different?  My situations
> is that I have developers who want to publish remote repositories that
> others can contribute to.
>
> Thanks,
>
> Sean
>