300891 - Lack of chrome/global.dtd in en-GB locale causes build failure.

Status: RESOLVED FIXED

(Firefox Build System :: General, defect)

Description

[Colin Harrison]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322)
Build Identifier: CVS

Following a recent change in CVS (addition of file mozilla/dom/locales/en-
US/chrome/global.dtd), my CVS build using export MOZ_CO_LOCALES="en-GB" fails, 
can't find "global.dtd".
The make works if I copy the file:-
cp mozilla/dom/locales/en-US/chrome/global.dtd l10n/en-GB/dom/chrome/global.dtd

File only contains:-<!ENTITY locale.dir "ltr">.



Reproducible: Always

Steps to Reproduce:
1. Latest CVS (Fri Jul 15 10:25:00 BST 2005) co
2. configure/build using MOZ_CO_LOCALES="en-GB"
3.

Comment 1

[Colin Harrison]

The fixes to bug 299480 are where the file global.dtd was created. This report 
is therefore duplicate?

Comment 2

[Mark Tyndall]

I'm afraid that localised trunk versions will often stop building because of
changes to the main (en-US) tree that aren't immediately reflected in the l10n tree.

This particular problem was fixed this morning - see
<http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-en-GB> (which is
currently, fleetingly green) - but any new file in  */locales/en-US/* will turn
the l10n tinderboxen red.

Comment 3

[Reed Loden [:reed]]

The patch in bug 299480 seems to have fixed this problem.