Closed Bug 298769 Opened 20 years ago Closed 19 years ago

In </chrome/US.jar>, 2 "Error: no element found"

Categories

(SeaMonkey :: Installer, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
seamonkey1.0alpha

People

(Reporter: sgautherie, Assigned: kairo)

References

Details

Attachments

(1 file, 1 obsolete file)

[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b2) Gecko/20050625] (nightly) (W98SE)

First (Browser) startup:

{{
Error: no element found
Source File: jar:resource:///chrome/US.jar!/locale/US/editor-region/contents.rdf
Line: 1

Error: no element found
Source File: jar:resource:///chrome/US.jar!/locale/US/editor-region/manifest.rdf
Line: 1
}}
Looks like fallout from bug 286108 - locale/US/editor-region/contents.rdf and
region.properties got put into comm.jar instead of US.jar by mistake.
Blocks: 286108
Component: Composer → Build Config
(In reply to comment #1)
> Looks like fallout from bug 286108 - locale/US/editor-region/contents.rdf and
> region.properties got put into comm.jar instead of US.jar by mistake.

[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b2) Gecko/20050625] (nightly) (W98SE)

'content/' file is in <comm.jar>,
'locale/' files are in <en-US.jar>.

Workaround:
This change to <installed-chrome.txt> (and deleting <chrome.rdf> to be sure)
fixes this bug
{{
-locale,install,url,jar:resource:/chrome/US.jar!/locale/US/editor-region/
+locale,install,url,jar:resource:/chrome/en-US.jar!/locale/en-US/editor-region/
}}

Then I don't know if the files need to be moved, or the chrome registration
updated: I leave it to you.
Component: Build Config → Installer
Flags: blocking-seamonkey1.0a?
Flags: blocking-seamonkey1.0a? → blocking-seamonkey1.0a+
(In reply to comment #2)
>'content/' file is in <comm.jar>,
>'locale/' files are in <en-US.jar>.
Yes, but -region files go in <US.jar>
This should do it. SeaMonkey still only supports building en-US, so it's OK to
hardcode the file to US.jar here for now (I'd love to get rid of the seperate
region and platforms packs one time anyways, then we also can get rid of that
hardcoding).

For now, we need the files in the old region/content pack location and this
moves them back there.
Assignee: composer → kairo
Status: NEW → ASSIGNED
Attachment #189425 - Flags: superreview?(neil.parkwaycc.co.uk)
Attachment #189425 - Flags: review?(benjamin)
Comment on attachment 189425 [details] [diff] [review]
patch: move region locale back to US.jar

The zip path is still locale/en-US/editor-region
Attachment #189425 - Flags: superreview?(neil.parkwaycc.co.uk) → superreview-
Argh, sure, have to adjust the path as well... Done in this version...
Attachment #189425 - Attachment is obsolete: true
Attachment #189460 - Flags: superreview?(neil.parkwaycc.co.uk)
Attachment #189460 - Flags: review?(benjamin)
Attachment #189425 - Flags: review?(benjamin)
Attachment #189460 - Flags: superreview?(neil.parkwaycc.co.uk) → superreview+
Attachment #189460 - Flags: review?(benjamin) → review+
Comment on attachment 189460 [details] [diff] [review]
patch v2: also change path back to US
[Checked in: Comment 8]

'approval1.8b4=?': (SeaMonkey only)
Trivial installer fix, no risk.
Attachment #189460 - Flags: approval1.8b4?
Attachment #189460 - Flags: approval1.8b4? → approval1.8b4+
checked in, this should be FIXED now ;-)
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Attachment #189460 - Attachment description: patch v2: also change path back to US → patch v2: also change path back to US [Checked in: Comment 8]
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b4) Gecko/20050720 SeaMonkey/1.0a]
(nightly) (W98SE)

V.Fixed.
Status: RESOLVED → VERIFIED
Target Milestone: --- → Seamonkey1.0alpha
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: