https://bugzilla.wikimedia.org/show_bug.cgi?id=70446
Bug ID: 70446
Summary: Are Scap and LocalisationUpdate actually fighting over
l10nupdates?
Product: Wikimedia
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: Unprioritized
Component: Deployment systems
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected],
[email protected], [email protected],
[email protected]
Blocks: 70443
Web browser: ---
Mobile Platform: ---
So Bryan and I were looking at the l10nupdate scripts, noticing that it's
essentially a reproduction of what's in scap.
For a little work, it was possible to make l10nupdate quicker, but there's a
lot of code in it that should be replaceable with a scap call.
When we started digging into this a bit further, we have come to a conclusion
that any scap run after an l10nupdate is possibly wiping out any changes made
by them. This is due to different cache directories being used to build l10n
caches from... Causing untold bugs?
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
