Closed Bug 10129 Opened 25 years ago Closed 25 years ago

[feature] Version Registry: Package node not created after triggering jar file

Categories

(Core Graveyard :: Installer: XPInstall Engine, defect, P3)

PowerPC
Mac System 8.5
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jimmykenlee, Assigned: dveditz)

References

Details

(Keywords: platform-parity)

Build: 7/16/99 SeaMonkey build 1. Backup or remove Netscape Registry from System Folder:Preferences for simplicity 2. Install 4.5, 4.61, or 4.7, launch and exit 3. SeaMonkey Macintosh does not have an installer yet, so just launch apprunner 4. Go to http://jimbob/jars/trigger2.html 5. Trigger any relative path jar like a_adddelcomp.jar 6. Exit and launch 4.x 7. Open http://slip/softupdate/BiggerRegToy.html and check the Version Registry for Communicator (or the node that corresponds to 4.x) RESULT: The Install.log indicates that the installation was successful. The file appears to be installed in the correct location. There is no package node in the Netscape Registry that corresponds to 5.0. There is a registry setting, "acceptance", from Communicator (or 4.x package node) that corresponds to the the jar triggered from 5.0. EXPECTED RESULT: From Netscape Registry, a package node that corresponds to 5.0 with a registry setting that corresponds to the triggered jar. Components should not be registered in other package nodes. They should at least fail.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I think that I have fixed this a few days a go. Today's build should have the fix in it. Can you verify?
Status: RESOLVED → REOPENED
Build 7/22/99 The problem still exists as described originally.
Resolution: FIXED → ---
Clearing Fixed resolution due to reopen.
Severity: major → critical
Priority: P3 → P1
Hard to believe this is only on Macintosh
Blocks: 11020
Summary: [PP]Version Registry: Package node not created after triggering jar file → [feature] [PP]Version Registry: Package node not created after triggering jar file
Target Milestone: M11
Blocks: 12805
Target Milestone: M12 → M13
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall Engine
Target Milestone: M13 → M14
Keywords: pp
Priority: P1 → P3
Summary: [feature] [PP]Version Registry: Package node not created after triggering jar file → [feature] Version Registry: Package node not created after triggering jar file
we think this is fixed. Jimmy, please help verify. ~ thanks!
Status: ASSIGNED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
Build 2000-03-21-05-M15-nb1b (Mac) Currently, we register only the package node. This has been working for a long time now. 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.