Closed Bug 458017 Opened 16 years ago Closed 16 years ago

Increment Fennec BuildID separately

Categories

(Firefox for Android Graveyard :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: tonikitoo, Assigned: mfinkle)

Details

Attachments

(3 files, 1 obsolete file)

Attached image xml parser error 1
run a raw build from tonight's tip (rev 214:5f94200eb710).

prefs xbl's seems problematics. 

see sshot 1 and 2.
Attached image xml parser error 2
This sounds like fallout from bug 455145. I saw similar errors. The problem was the XUL cache in my profile. The BUILDID of Fennec wasn't being bumped up in my test, so the cache was stale. Deleting my profile "fixed" the problem. Another way to fix the problem is to get the BUILDID in application.ini bumped up.

Let me know if that fixes things for you.
I don't see this problem at all. preferences.dtd is there, and it doesn't appear to be missing anything: http://hg.mozilla.org/mobile-browser/file/5f94200eb710/locales/en-US/chrome/preferences.dtd
works after a clobber build.

invalid.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
What is a clobber build?

I just did the fennec update and I am getting the XML parsing error in chrome://browser/content/browser.xul ?
Niranjan: a clobber build is just basically deleting your objdir or running make distclean and rebuilding... as opposed to a depend build.  Something isn't getting rebuilt correctly
It works after making a fresh build.
I'm reopening after seeing something similar

> XML Parsing Error: undefined entity
> Location: chrome://browser/content/browser.xul
> Line Number 96, Column 5:    <command id="cmd_openLocation" label=" openLocation.label;" oncommand="CommandUpdater.doCommand(this.id);"/>
> ----^
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
deleting my profile fixed the problem, sounds like mark was right in comment #2.  It would still be nice to get this fixed.
Attached patch patch (obsolete) — Splinter Review
Switch to an app-specific build-id and not a GRE build-id. Similar code was added to other XULRunner apps, especially where the SDK is used to build.

Now anytime the app is rebuilt and XR doesn't, we still increment the buildid in application.ini
Assignee: nobody → mark.finkle
Attachment #350433 - Flags: review?(gavin.sharp)
Should we use make-platformini.py --print-buildid instead, to match what xulrunner does? Not sure how portable that date call is...

http://mxr.mozilla.org/mozilla-central/source/config/Makefile.in#116
Attached patch patch 2Splinter Review
This one uses make-platformini.py --print-buildid
Attachment #350433 - Attachment is obsolete: true
Attachment #350719 - Flags: review?(gavin.sharp)
Attachment #350433 - Flags: review?(gavin.sharp)
Comment on attachment 350719 [details] [diff] [review]
patch 2

>diff --git a/app/Makefile.in b/app/Makefile.in

>-DEFINES += -DGRE_MILESTONE=$(GRE_MILESTONE) -DGRE_BUILDID=$(GRE_BUILDID) -DAPP_NAME=$(MOZ_APP_DISPLAYNAME)
>+DEFINES += -DGRE_MILESTONE=$(GRE_MILESTONE) -DGRE_BUILDID=$(GRE_BUILDID)  -DAPP_BUILDID=$(APP_BUILDID)

nit: extra space
Attachment #350719 - Flags: review?(gavin.sharp) → review+
removed extra space

http://hg.mozilla.org/mobile-browser/rev/29cf79de7ea5
Status: REOPENED → RESOLVED
Closed: 16 years ago16 years ago
Resolution: --- → FIXED
Summary: XML parser error in fennec's browser.xml → Increment Fennec BuildID separately
verified with beta4
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: