Making Centralized Arch Repositories Tolerable

Some people think that having multi-committer Arch repositories is evil. Others attempt to deal with the failings of SFTP by installing a wrapper to set the umask. This is would be an insane workaround for arch.debian.org, so what I and others like to do is make use of ACLs to avoid the headaches which one might otherwise face.

For example, if one had a repository in /arch/dbnpolicy/hamm , one could run

setfacl -R -m 'g:dbnpolicy:rwX' /arch/dbnpolicy/hamm

setfacl -R -d -m 'g:dbnpolicy:rwX' /arch/dbnpolicy/hamm

The -d is the magic here; it ensures that all new patches will be writable by the dbnpolicy group. This is important because each member of that group needs to be able to manipulate Arch lockfiles.

Have fun.

UPDATE: Daniel Stone correctly points out that the « rwX »'s above, which were « rwx »'s, should be « rwX », as they are now.