Mercurial ACL prevents pull
Please help me with understanding the mechanics behind Mercurial in combination with ACL.

Our team uses Mercurial as a versioning system. The setup is very simple: two developers (one linux, one windows), remote repo (linux). Every time, the windows user **W** checks in modifications and the linux user **L** wants to pull afterwards, the following error messages (depending on the altered file(s)) are displayed:

>     pulling from ssh://user@domain.com
>     searching for changes
>     adding changesets
>     transaction abort!
>     rollback completed
>     abort: stream ended unexpectedly (got 0 bytes, expected 4)
>     remote: abort: Permission denied: /repopath/.hg/store/data/paper/tmp.txt.i

This is because the file access is handled by linux's ACL lists. After the ACL permissions are corrected with the `setfacl` command, everything runs smooth and **L** is able to pull. Even if **W** clones the repo with correct permission, the (new/ modified) files in the `.hg` directory have the wrong (default) permissions. The parent folder of the repo has the correct permission set, so I don't know from where those permissions are inherited.

Did somebody face similar problems? Thank you in advance!
Mercurial ACL prevents pull
===

Please help me with understanding the mechanics behind Mercurial in combination with ACL.

Our team uses Mercurial as a versioning system. The setup is very simple: two developers (one linux, one windows), remote repo (linux). Every time, the windows user **W** checks in modifications and the linux user **L** wants to pull afterwards, the following error messages (depending on the altered file(s)) are displayed:

>     pulling from ssh://user@domain.com
>     searching for changes
>     adding changesets
>     transaction abort!
>     rollback completed
>     abort: stream ended unexpectedly (got 0 bytes, expected 4)
>     remote: abort: Permission denied: /repopath/.hg/store/data/paper/tmp.txt.i

This is because the file access is handled by linux's ACL lists. After the ACL permissions are corrected with the `setfacl` command, everything runs smooth and **L** is able to pull. Even if **W** clones the repo with correct permission, the (new/ modified) files in the `.hg` directory have the wrong (default) permissions. The parent folder of the repo has the correct permission set, so I don't know from where those permissions are inherited.

Did somebody face similar problems? Thank you in advance!