167172 - Lack of .jst file in cvs repository causes incorrect install.js to be substituted,

Status: RESOLVED INVALID

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

Description

[Aaron Leventhal]

When I accidentally failed to checkin typeaheadfind.jst, everything looked good
until I tried to install.

The installer did not complain about the lack of the correct install.js file.
This is because a different, and incorrect install.js file was substituted in
place of the missing one.

The install log should have shown an error of some kind, instead of having the
appearance of success.

Comment 1

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 2

[Serge Gautherie (:sgautherie)]

I assume this was/is a Core (feature) bug...
If not, please give some hints and move this bug back to SeaMonkey. Thanks.

Comment 3

[Dave Townsend [:mossop]]

Whatever it is it is too old to be relevant