Last modified: 2014-08-26 00:37:04 UTC
sync-common and mw-update-l10n were split apart to make things work a little bit faster during a full scap. This is great, but it has a unintended side effect. Deployers (and puppet) mostly assume that sync-common is all that is needed to update a host with the deploy master. Nobody remembers that you now have to run mw-update-l10n too. This sucks and we can do better. * Change logic in sync-common to run mw-update-l10n steps after sync is complete * Add command line option `--no-update-l10n` to preserve the existing behavior * Change `scap` to call `sync-common --no-update-l10n` to preserve the existing behavior
Ori would really like this to have been done already and I don't disagree, so I'm setting the importance to high and starting work on it.
Change 155677 had a related patch set uploaded by BryanDavis: Make sync-common update l10n cdb files by default https://gerrit.wikimedia.org/r/155677
Change 155677 merged by jenkins-bot: Make sync-common update l10n cdb files by default https://gerrit.wikimedia.org/r/155677