Multi-user Mercurial repositories over SSH? -
I have a centralized mercury repository that I want to provide access through SSH.
I have a Chown Route: developers at the repository-R repository directory, so all users of the group 'developers' should be using.
So, I clone, my initial files are user A, commit, pushed, done. Now, I go as user b, clone, add a file, commit and push. But then, when I make a bridge, I make an update and change that file as User A and then try to push me,
for changes / var Clicking on / hg / repository 1 changes found to add changes adding file changes transaction canceled! Rollback completed: Permission denied: /var/hg/repository/.hg/store/data/test.i
Am I missing a configuration step? Should not I use SSH?
Edit I've found that using sticky bits solves the problem: is this a bad solution?
Sticky group bits are the right way to do this; In addition to this, it was such a matter that the user's peer It is important to determine that the group will be reading / writing for new files, but for the last year or two mercurial copies, the permissions of the .hg directory (not owned) are made in newly created files, hence the output is not important.
Comments
Post a Comment