For the upcoming SeaMonkey 2.1, the have been string changes in Chatzilla since the last signed-off revision: Comparing nb-NO to en-US Properties in ./chrome/chatzilla.properties don't match: In ./en-US: (add these to your localization) cmd.goto-startup.label cmd.goto-startup.help msg.logging.icon.off msg.logging.icon.on In /builds/slave/comm-2.0-lnx-l10n-dep/build/releases/l10n-mozilla-2.0/nb-NO/extensions/irc: (remove these from your localization) msg.network.opened msg.channel.opened msg.query.opened make: *** [libs] Error 1 I plan to spin 2.1 early tomorrow, [sunday latest] so unless you get the necessary string changes into venkman by then, I will commit (temporarily) en-US copies (and remove the necessary string) for the 2.1 release, and backout after the relbranch is created
Alternate solution, per KaiRo... We'll disable cZ (and venkman if necessary) from the extension repos on the SeaMonkey2.1 relbranch. And I'll trigger a build to verify things are good. We'll use the |default| revision on nb-NO for l10n-mozilla-2.0, which is the same revision that was signed off for Firefox 4.0.1 We will be forced to mark nb-NO as a "beta" quality localisation of SeaMonkey on the release page[s] at this time. [CC-ing Jens, for the detail of marking this locale as beta-quality.]
(In reply to comment #1) > Alternate solution, per KaiRo... > > We'll disable cZ (and venkman if necessary) from the extension repos on the > SeaMonkey2.1 relbranch. And I'll trigger a build to verify things are good. > After re-reading this, I note its not clear what I meant. We'll disable localization for cZ and (if necessary) venkman, not the extensions themselves. They will remain shipped, but with en-US localization instead
http://hg.mozilla.org/chatzilla/rev/210002e2b7e7 (relbranch) http://hg.mozilla.org/chatzilla/rev/8881664ea740 (default, so I could test) http://hg.mozilla.org/chatzilla/rev/3ce6261ee304 (backout on default) Was able to complete the l10n build with cZ using en-US with this.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.