Rebase Permissions

[Matt Mackall]

On Mon, 2009-11-02 at 14:27 -0800, Stephen Rasku wrote:
> I am trying to rebase a repository that I didn't create but which I
> have group write permission on:
> 
> $ ls -l .
> total 40
> drwxrwxr-x 114 hguser hg 4096 Nov  2 14:17 Dir1/
> drwxrwxr-x   7 hguser hg 4096 Sep 10 15:43 Dir2/
> drwxrwxr-x   2 hguser hg 4096 Oct 15 07:58 INC/
> drwxrwxr-x   2 hguser hg 4096 Sep 10 15:43 psftp/
> drwxrwxr-x  11 hguser hg 4096 Sep 10 15:43 www/
> 
> When I try and rebase it, I get the following error:
> 
> $ hg pull --reb
> pulling from /var/hg/blah
> searching for changes
> adding changesets
> adding manifests
> adding file changes
> added 159 changesets with 411 changes to 171 files (+1 heads)
> (run 'hg heads' to see heads, 'hg merge' to merge)
> abort: Permission denied: /.../Dir1/newmodule/Makefile
> 
> This module doesn't exist in the repository prior to rebasing.  Why
> would Mercurial create a file with permissions that the user running
> the command can't use?

Mercurial does very little with permissions, so this is surprising.
What permission/ownership does that file end up getting? What filesystem
is involved?


-- 
http://selenic.com : development and support for Mercurial and Linux