Open Bug 1255825 Opened 9 years ago Updated 3 years ago

L10n repacks should fail if they're missing strings

Categories

(Firefox Build System :: General, defect)

defect

Tracking

(Not tracked)

People

(Reporter: catlee, Unassigned)

References

Details

(not sure if this is the right component or not - feel free to move somewhere else. build config maybe?) We hit this in bug 1255811 - some locales ended up with missing strings, and we didn't find out until we were right at the point of shipping. The repack process should fail if we're expecting to merge in en-US strings, but don't for some reason.
Yeah, let's say toolkit build config. Note, I don't have a good idea if this is feasible. We've worked hard to make them unfallible, and now they are. Related thoughts: Reducing the pieces that can break might be a good alternative. I filed bug 1255822 ad-hoc, to make us not depend on windows paths and shells. There's the infamous bug 1107635 to get rid of make and put everything into python, too.
Component: Automation → Build Config
Product: Localization Infrastructure and Tools → Toolkit
Right now, compare-locales only creates the merge dir if it actually needs to write to it, so doing so will require us being able to update compare-locales, likely bug 1223385 is required for that.
Triaging an old bucket to be closed - Catlee is this bug still and issue?
Flags: needinfo?(catlee)
I don't know, Axel is probably a better judge of if this is still a problem.
Flags: needinfo?(catlee)
Flags: needinfo?(l10n)
With updating compare-locales, the l10n merge directory will become non-optional, so doing something like in comment 2 will become totally feasible. I'm just preparing a drop in bug 1478343.
Blocks: 1478343
Flags: needinfo?(l10n)
No longer blocks: 1478343
Depends on: 1478343
Component: Build Config → General
Product: Toolkit → Firefox Build System
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.