Closed
Bug 627455
Opened 13 years ago
Closed 13 years ago
Lots of L10n repack failures after omnijar switch
Categories
(SeaMonkey :: Build Config, defect)
SeaMonkey
Build Config
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey2.1b2
People
(Reporter: kairo, Assigned: kairo)
References
Details
(Keywords: regression)
Attachments
(1 file)
|
877 bytes,
patch
|
Callek
:
review+
|
Details | Diff | Splinter Review |
I tried to make L10n repacks work fine with omni.jar and I mostly have succeeded, but what I didn't look at is repeated L10n repacks for different locales from the same directory structure, which is what our buildbots do. There seems to be a small glitch (missed porting from l10n.mk) that makes those fail. I *should* have a patch for that, but I'm trying to confirm on a slave right now.
|
Assignee | |
Comment 1•13 years ago
|
||
This ports the missing l10n.mk hunk from http://hg.mozilla.org/mozilla-central/rev/d37b6b337227 to suite/ as we're not using l10n.mk yet. I tested that it works on a slave with the steps our factories are applying.
Attachment #505475 -
Flags: review?(bugspam.Callek)
|
||
Updated•13 years ago
|
Attachment #505475 -
Flags: review?(bugspam.Callek) → review+
|
|
Assignee | |
Comment 2•13 years ago
|
||
Thanks for the fast review, pushed as http://hg.mozilla.org/comm-central/rev/1025dd5f0c49
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Summary: Lot of L10n repack failure after omnijar switch → Lots of L10n repack failures after omnijar switch
Target Milestone: --- → seamonkey2.1b2
|
||
Updated•13 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•