Closed Bug 174619 Opened 23 years ago Closed 23 years ago

Installed-chrome.txt in MFCEmbed is incorrect file

Categories

(Core Graveyard :: Installer: MFCEmbed, defect)

x86
Windows 2000
defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.2beta

People

(Reporter: carosendahl, Assigned: asasaki)

Details

Attachments

(2 files)

The Installed-chrome.txt file that is currently packaged as part of the mfcembed (GRE version) installer is the wrong one. The correct file is the same as the installed-chrome.txt file found in the 10-11-2002 builds.
Status: NEW → ASSIGNED
Upping severity and setting Target Milestone.
Severity: normal → blocker
Target Milestone: --- → mozilla1.2beta
Attached patch Patch 1Splinter Review
I was most certainly getting the file from the wrong place.
I'm going to need Aki to add the following two lines to the appropriate place in build-verification.pl also: + &genericlog ("$ENV{MOZ_SRC}\\mozilla\\xpinstall\\packager\\pkgcp.pl --source $ENV{MOZ_SRC}\\mozilla\\dist\\gre_app_support --destination $ENV{MOZ_SRC}\\stage\\mfcembed --file $ENV{MOZ_SRC}\\mozilla\\xpinstall\\packager\\pkgs2-mfcembed-win --os dos --verbose \n"); + system ("$ENV{MOZ_SRC}\\mozilla\\xpinstall\\packager\\pkgcp.pl --source $ENV{MOZ_SRC}\\mozilla\\dist\\gre_app_support --destination $ENV{MOZ_SRC}\\stage\\mfcembed --file $ENV{MOZ_SRC}\\mozilla\\xpinstall\\packager\\pkgs2-mfcembed-win --os dos --verbose 2>&1 ") &&
r=asasaki do you have write access to the ns tree? ns/build/windows/verification/build-verification.pl i can update the build machine once you check in.
Sure. I just don't usually mess with your build files. Let me get an sr=, then I'll check my stuff in tomorrow and you can apply this patch to the build machine, too. Thanks.
Comment on attachment 102991 [details] [diff] [review] Patch 1 sr=leaf, just change the silly new filename
Attachment #102991 - Flags: superreview+
Comment on attachment 103011 [details] [diff] [review] build-verification.pl patch 1 sr=leaf, likewise, change the reference to the silly newfilename
Attachment #103011 - Flags: superreview+
I checked in both patches. Reassigning to Aki so he can close it after updating the build machine and doing a test run.
Assignee: curt → asasaki
Status: ASSIGNED → NEW
looks like it worked. i'm using the 2002-10-16-17-trunk build, but y'all should see it in tomorrow morning's builds as well.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Verified - 20021017 build
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: