Closed
Bug 472431
Opened 16 years ago
Closed 16 years ago
Localized builds have chrome.manifest & install.rdf at root level
Categories
(Firefox Build System :: General, defect, P1)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla3.1b3
People
(Reporter: nthomas, Assigned: Pike)
References
Details
(Keywords: regression)
Attachments
(2 files, 1 obsolete file)
1.39 KB,
patch
|
Pike
:
review+
beltzner
:
approval1.9.1+
|
Details | Diff | Splinter Review |
315 bytes,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
If you unpack a latest-mozilla-central-l10n/ or latest-mozilla-1.9.1-l10n/ build for a locale then you'll get a chrome.manifest and install.rdf, which appear to be from the associated langpack. These aren't present in en-US nightlies or 3.0.5 builds, but can also be found in 3.1b2. Even if this doesn't break the app, I think we ought to fix it because it introduces a bogus difference between en-US and l10n builds.
Fallout from bug 458014 ?
Reporter | ||
Updated•16 years ago
|
Summary: Locale builds have chrome.manifest & install.rdf at root level → Localized builds have chrome.manifest & install.rdf at root level
Assignee | ||
Comment 1•16 years ago
|
||
Found the bug, taking.
Assignee | ||
Comment 2•16 years ago
|
||
Simple patch, once I found where we actually copy over. Asking Nick for review to not make Ted cry.
Attachment #357285 -
Flags: review?(nthomas)
Reporter | ||
Comment 3•16 years ago
|
||
I'm not familiar with this code. Ben I think you might know more, would you mind taking the review ?
Does this cover the Mac case too ? All three platforms are affected.
Assignee | ||
Comment 4•16 years ago
|
||
Actually, all four binaries are affected. All three packages (tar, zip, dmg) are covered by the repackage-zip tweak, and the windows installer by the repackage-win32-installer tweak.
PS: When testing this, you need to clobber l10n-stage. Local builds don't do that on purpose, but that happens anyway when a new en-US binary comes in to get repackaged by the deps.
Assignee | ||
Updated•16 years ago
|
Attachment #357285 -
Flags: review?(nthomas) → review?(bhearsum)
Comment 5•16 years ago
|
||
Comment on attachment 357285 [details] [diff] [review]
don't copy over install.rdf and chrome.manifest for installers and packages
>diff --git a/browser/locales/Makefile.in b/browser/locales/Makefile.in
>--- a/browser/locales/Makefile.in
>+++ b/browser/locales/Makefile.in
>@@ -226,7 +226,10 @@
> $(CYGWIN_WRAPPER) 7z x -ol10n-stage $(WIN32_INSTALLER_IN)
> $(RM) -r l10n-stage/localized
> $(RM) l10n-stage/setup.exe
>+# copy xpi-stage over, but not the langpack files
>+# install.rdf and chrome.manifest
This comment is a little unclear to me. Maybe you can drop 'the langpack files' and just leave the names ?
>+# copy xpi-stage over, but not the langpack files
>+# install.rdf and chrome.manifest
same here.
Looks fine otherwise.
Attachment #357285 -
Flags: review?(bhearsum) → review+
Reporter | ||
Comment 6•16 years ago
|
||
*nudge* Please land this fix before 3.1b3 comes along.
Reporter | ||
Comment 7•16 years ago
|
||
Looks like this landed in m-c:
http://hg.mozilla.org/mozilla-central/rev/8fe5bc1ec5e9
so please take comment #6 for mozilla-1.9.1
Of course it's hard to tell if it's working because we're not pulling m-c properly when building locales - bug 474898.
Assignee | ||
Comment 8•16 years ago
|
||
This is the patch that I landed. I reworded the comment to be clearer which files we don't copy over, but kept referencing langpack as the reason why.
Verified the fix against my l10n builds. Those just finished the first build with the new nightlies, which I needed as I compile with the nightly en-US sources in the end.
Requesting approval1.9.1 as we want this for Beta 3.
Attachment #357285 -
Attachment is obsolete: true
Attachment #358381 -
Flags: review+
Attachment #358381 -
Flags: approval1.9.1?
Assignee | ||
Updated•16 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Flags: blocking-firefox3.1?
Resolution: --- → FIXED
Assignee | ||
Updated•16 years ago
|
Status: RESOLVED → VERIFIED
Assignee | ||
Updated•16 years ago
|
Priority: -- → P1
Target Milestone: --- → Firefox 3.1b3
Comment 9•16 years ago
|
||
Comment on attachment 358381 [details] [diff] [review]
patch that landed, with better comments
a191=beltzner
Attachment #358381 -
Flags: approval1.9.1? → approval1.9.1+
Assignee | ||
Comment 10•16 years ago
|
||
Keywords: fixed1.9.1
Updated•16 years ago
|
Flags: blocking-firefox3.1? → blocking-firefox3.1+
Reporter | ||
Comment 11•16 years ago
|
||
I'd like to remove the two files on update to 3.1b3 too, it's adding noise to our update verifications and we should keep everyone in sync.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 12•16 years ago
|
||
Attachment #360837 -
Flags: review?
Reporter | ||
Updated•16 years ago
|
Attachment #360837 -
Flags: review? → review?(ted.mielczarek)
Updated•16 years ago
|
Attachment #360837 -
Flags: review?(ted.mielczarek) → review+
Reporter | ||
Comment 13•16 years ago
|
||
Comment on attachment 360837 [details] [diff] [review]
Update removed-files.in
http://hg.mozilla.org/mozilla-central/rev/688c44602a55
Reporter | ||
Comment 14•16 years ago
|
||
Comment on attachment 360837 [details] [diff] [review]
Update removed-files.in
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/b42b29ee809b
Reporter | ||
Updated•16 years ago
|
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: Build Config → General
Product: Firefox → Firefox Build System
Updated•6 years ago
|
Keywords: fixed1.9.1,
regression
Target Milestone: Firefox 3.1b3 → mozilla3.1b3
Updated•6 years ago
|
Keywords: regression
You need to log in
before you can comment on or make changes to this bug.
Description
•