https://bugzilla.wikimedia.org/show_bug.cgi?id=71093

--- Comment #3 from Bryan Davis <[email protected]> ---
The git clone permissions problem may only affect my test box? I kind of
skipped over Yuri's analysis when I saw the same top level error message from
puppet. For me, the base directory at /srv/vagrant has the desired permissions
(2775) but the mediawiki clone at /srv/vagrant/mediawiki ended up with 2770
permissions. I fixed with `sudo chmod -R o+rX /srv/vagrant/mediawiki` which
gets me past that particular problem.

Once I had cleared the code readability hurdle, I hit the same issue that Yuri
reported. I think this issue is caused by
I86b110b6ac2e92f4796b94f82f8ffb59d2ae23e2 which switched the default l10n cache
behavior to use cdb files. In a VM-based MediaWiki-Vagrant deploy the /vagrant
directory would be mounted in such a way as to ignore the file permissions and
allow www-data to write to /vagrant/mediawiki/cache. On a Labs instance this is
not the case. There are a couple of ways this could be fixed, but the easiest
is probably to follow the lead of the logging permissions fix introduced in
I194d788d1254c1e05ea53937b4663faaed537b62 and grant www-data write permissions
to the /vagrant/mediawiki/cache directory.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to