Closed
Bug 14996
Opened 25 years ago
Closed 25 years ago
[PP] Registry node is lost after patching to same registry name
Categories
(Core Graveyard :: Installer: XPInstall Engine, defect, P3)
Tracking
(Not tracked)
People
(Reporter: jimmykenlee, Assigned: cathleennscp)
Details
Build: 10/27/99 SeaMonkey build
1. From http://jimbob/trigger2.html, trigger http://jimbob/jars/b4patch.xpi to
set up file to be patched
2. Checking Version registry appears correct here
3. From http://jimbob/trigger2.html, trigger http://jimbob/jars/afterpatch.xpi
to patch file
b4patch.xpi
-----------
Install.StartInstall("Functional: patch test", "/patchtest", "1.1.1.1", 0);
var f = Install.GetFolder("Program", "patchtest");
Install.AddSubcomponent("/patchtest", "1.1.1.1", "SimpleText", f, "", true);
afterpatch.xpi
--------------
Install.StartInstall("Functional: patch test", "/patchtest", "1.2.1.1", 0);
var f = Install.GetFolder("Program", "patchtest");
err = Install.Patch("/patchtest", "1.2.1.1", "NCSA Telnet 2.7b5x.gdf", f,
"SimpleText", true);
RESULT:
The patching appears to be successful. The Install.log is accurate. The
Version registry shows that the registry name "/patchtest" is gone after
triggering afterpatch.xpi.
EXPECTED RESULT:
From the Version registry, the registry name "/patchtest" is present with an
updated Version number.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Comment 2•25 years ago
|
||
Checked for duplication with bug# 14901
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall
Engine
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 4•25 years ago
|
||
Verified dupe of bug 14901
Version Registry: Registry info is lost after a patch
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•