2014-05-30 0:57 GMT+03:00 Bryan Davis <[email protected]>: > I think bug 65188 [0] is the solution suggested by Ori that you are > referring to. Would this alone be enough to fix the problems for > translatewiki.net? More directly, is translatewiki.net using the top > level composer.json file to manage anything other than extensions? In > the near term is there any better work around for you (and others in a > similar position) other than running `git update-index > --assume-unchanged composer.json` in your local checkout to make it > ignore anything that happens to composer.json?
Now that composer.json also includes dependencies for core, ignoring changes to it would also break things. To make things worse, I noticed on my development environment that our own scap-equivalent will just go on to run composer update even if the file conflicted. This causes it to remove the extensions and libraries we currently install via composer, also breaking the site. -Niklas _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
