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
Version: unspecified
Severity: enhancement