This is because the transif user does not have access to /srv/git/comps.git. I've enabled FS ACLs on /srv on hosted01 and hosted02 and ran setfacl -R -m u:transif:rwx comps.git.

A test submission to bn_IN.po just worked for me, let us know if there are any other issues.

It stopped working again. Same error message as above, "Sorry, your file could not be sent because of an error."

I think we had an ssh-agent not running. It should be working now.

Please re-open if it's not.

I'm not happy to say it, but I still get the error and it still doesn't work.

Looking at the filesystem for the comps.git directory, I'm guessing that the problem is that the default acls aren't set. So once someone makes a new commit to the repository, there are no fsacls on the new file. ricky do you remember if you ran setfacl twic, once to set the acls and the second time to set the default acls?

Replying to [comment:5 toshio]:

Looking at the filesystem for the comps.git directory, I'm guessing that the problem is that the default acls aren't set. So once someone makes a new commit to the repository, there are no fsacls on the new file. ricky do you remember if you ran setfacl twic, once to set the acls and the second time to set the default acls?
Ah, I only ran it once. Is this the correct command to run?
{{{
setfacl -dR -m u:transif:rwx comps.git
}}}

I've run the command, can you check and see if it works now?

Yes, it works. Thanks!

Cool, thanks for the fix, Toshio - closing this ticket.

Hey raven, I've just made a change to the acls because they were causing a script that checks the status of the git repositories to spew warnings. Looking at the acls I think transifex should still be able to commit to comps fine but if not, feel free to reopen this.

I'll attach the script I used so people can compare what it did to what we might actually need.

Short script to set acls for the comps git repository
allow.sh