Changes needed for Building SeaMonkey 2.35 with Chatzilla

NEW
Assigned to

Status

3 years ago
3 years ago

People

(Reporter: philip.chee, Assigned: rginda)

Tracking

Trunk

Firefox Tracking Flags

(firefox42 affected)

Details

(Reporter)

Description

3 years ago
Chatzilla:
Problem:
> Contract ID '@mozilla.org/commandlinehandler/general-startup;1?type=chat' was registered as a command line handler for entry 'm-irc', but could not be created.
Suggested Fix: Build from c65366e47dd2 (Bug 1148242 Build chatzilla-service.js again)
Note: Cannot build from a newer changeset due to incompatible build system changes.

Problem: Version on AMO is "0.9.91.1.1-signed"
Suggested Fix: use a relbranch off c65366e47dd2 and create a synthetic version "0.9.91.1.2"

Gijs: is this acceptable to Chatzilla owners?
I don't understand the problem. Please provide more context?
Flags: needinfo?(philip.chee)
(Reporter)

Comment 2

3 years ago
(In reply to :Gijs Kruitbosch from comment #1)
> I don't understand the problem. Please provide more context?
We are preparing to release SeaMonkey 2.35 which will ship with Chatzilla, DOMi. The build system changes to Chatzilla that work on comm-central/mozilla-central break when trying to build on comm/mozilla-release Chatzilla as part of SeaMonkey 2.35. I would like to build Chatzilla on changeset c65366e47dd2.

Optionally I'd like to set the version number to 0.9.91.1.2 so that it doesn't get "updated" to 0.9.91.1.1-signed on AMO which doesn't have the fix for Bug 1148242. This isn't crucial - nobody seems to have noticed that missing but it would be nice to have at least until a newer version of Chatzilla gets uploaded to AMO.
Flags: needinfo?(philip.chee)

Comment 3

3 years ago
What are you currently building instead of c65366e47dd2? I'm happy for you to use whatever is good for you between the latest tagged release and tip, including latest tagged release with cherry picked build fixes. If rolling a new CZ release from tip would be helpful, let me know.
You need to log in before you can comment on or make changes to this bug.