Update.html to new build fails since regus.xpi is not installed

VERIFIED FIXED in mozilla0.8.1

Status

Core Graveyard
Installer: XPInstall Engine
P1
blocker
VERIFIED FIXED
17 years ago
2 years ago

People

(Reporter: Jimmy Lee, Assigned: tao)

Tracking

Trunk
mozilla0.8.1

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: pending for r,sr)

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
Build: 2001-02-28-15-Mtrunk(WIN), 2001-02-28-09-trunk(MAC), not tested on Linux, 
but I can see regus.xpi in the nscp-xpi subdirectory

1. Install 2001-02-28 build (make it simple by installing Navigator only)
2. Open any update.html such as 
ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/2001-02-27-13-Mtrunk/
update.html for Windows
3. Update Navigator, Cartman, and Aol on Desktop to match a Navigator only 
install from the install wizard

RESULT:
Different things have happened.  You may crash during update.  You may complete 
install, but upon restarting the browser menus may be incomplete.

A closer look at the install.log reveals that regus.xpi was not installed.

For WinNT, I manually installed regus.xpi followed by running the update.html as 
described in step #3.  Upon completing the update, restarting Netscape appears 
to show that everything upgraded successfully.  Therefore, it appears that this 
may be the reason for the failed installation using update.html only.

For Mac, restarting after running update.html appears to look normal.  But I 
know that regus.xpi was not installed (checking install.log).  This one is 
tricky because this is an incomplete upgrade even though everything appears 
"normal".  These are the ones that can slip by if I'm not awake.

EXPECTED RESULT:
regus.xpi should be installed when update.html is used to upgrade to a new 
build.

If update.html is going to be used for internal testing, we need this page to be 
maintained as related changes are made.  It's risky for QA to promote within if 
this page is not maintained to match changes made to the xpi packages.
(Reporter)

Comment 1

17 years ago
Nominating for beta.  XPInstall QA uses this update.html as a tool for testing 
upgrades.  We need this tool to accurately represent a real upgrade scenario.
Keywords: nsbeta1
have to do it.
Assignee: dbragg → dveditz
Severity: major → blocker
Keywords: nsbeta1 → nsbeta1+
Priority: -- → P1
Target Milestone: --- → mozilla0.8.1
(Assignee)

Comment 3

17 years ago
Assign to me if you'd like me to take it!
Ok, you've got it. Thanks!

I guess regus.xpi should be added to the special-cased "browser" files that 
don't get a separate checkbox, since the browser won't run correctly without 
it.
Assignee: dveditz → tao
(Assignee)

Comment 5

17 years ago
Created attachment 26590 [details] [diff] [review]
add regus.xpi to update.html (for ns mac/win)
(Assignee)

Comment 6

17 years ago
Hi, folks:

Mind to give r/sr on the patch above?
Status: NEW → ASSIGNED
Whiteboard: pending for r,sr
(Assignee)

Comment 7

17 years ago
fixed in 61626's patches.
Status: ASSIGNED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
(Reporter)

Comment 8

17 years ago
Build: 2001-03-06-11-Mtrunk(WIN), 2001-03-06-10-trunk(MAC)

Back to normal.  Most excellent!  Marking Verified!
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.