[Sorry this has taken so long. Work was been eating my time.] Here is my list of current outstanding issues with Gitosis. I do not have fixes for these at the moment, but people and web indexes should be aware of the problems. The author of Gitosis seems to have been taken off-line. (The list may not be complete. I may have forgotten something.) 1. Multiple duplicate keys parsing problem This can happen when you have multiple people administering a repository. (Especially when those people are responsible for separate projects on the same server. You have a.pub and b.pub. These are both the public key for "Bob". (The same exact key in two files.) Any group that a.pub is added to Bob will have access to. Any group that b.pub is added to that does not contain a.pub Bob will not have access to. (It seems to sort the keys and only sees the first occurrence of the key, not all occurrences. 2. Trees with working directories kills Gitosis If any of the repositories in the repository have a working directory, Gitosis will fail on a push to gitosis-admin with a bunch of Python barfage. (I don't have an example at hand, but if you look at the code, it is looking at ".git".) This usually happens when someone tries to shortcut the process by cloning code into the repo on the local machine. 3. Gitosis needs to have access to everything. If your mount point for the repository is /repo you have to create a directory under this, else /repo/lost+found prevents Gitosis for initializing correctly. It is a permissions issue. 4. Typos are deadly. If you push a gitosis.conf file to gitosis-admin that has a non-parseable typo, gitosis will have problems. The immediate effect is that the authorized-keys file does not get updated. (New keys do not get added to the file, but existing ones work up except for the typo areas.) The only way to fix this is to hand-correct the copy on the server. Rerunning the gitosis-init script on the server will fix a lot of problems and does not overwrite existing configs. Those are the ones I can remember at the moment. As soon as I send this I will remember more. Hope this helps. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html