Experimental SeaMonkey 2.35-gamma builds **Please Read**

http://seamonkey.callek.net/contrib/
http://seamonkey.callek.net/contrib/seamonkey-2.35.en-US.win32-20150626.zip

I am currently building test 2.35 builds using comm-release tip and
mozilla-esr38 + THUNDERBIRD_38_VERBRANCH.

I've tested this build lightly and have not noticed any problems (yet).

My main problem was getting Chatzilla and DOMI to build. Due to
incompatible changes in the moz.build process on trunk. Chatzilla and
DOMI cannot be built off tip.

My notes so far.

DOMi:
Problem: Contract ID
'@mozilla.org/commandlinehandler/general-startup;1?type=inspector' was
registered as a command line handler for entry 'm-inspector', but could
not be created.

Simplest fix:
Build from 80c195824f1e (Bug 1147685 Build inspector-cmdline.js)
Leaving DOMi Version at 2.0.16pre
  Also note version number has to be > 2.0.15.1 to prevent updating from
AMO to 2.0.15.1-signed which doesn't have the cmdline fix.
  Note: Ratty has uploaded DOMI 2.0.16 to AMO but don't know when it
will get reviewed (129 out of 130 in queue).
  Note: Cannot build with any newer revision as bug 1158751 (Port
NO_JS_MANIFEST changes) is incompatible with the
comm-release/mozilla-release build system.

Slightly more complicated fix:
1 Create a relbranch off dfad1b2e38e4 (Tag: DOMI_2_0_16).
2 on this branch backout some build system changes:
2.1 (9af90c864080) Bug 1158751 - Port NO_JS_MANIFEST changes
2.2 (35e42668e631) Bug 1158774 - Port |Bug 1155776 - move
USE_EXTENSION_MANIFEST to moz.build| to comm-central
2.3 (a60fa07fdae5) Bug 1162694 - Remove XULAPP_DEFINES from DOM Inspector
This should allow comm-release to build DOMI 2.0.16

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 bump the version to
"0.9.91.2"

Phil

-- 
Philip Chee <philip@aleytys.pc.my>, <philip.chee@gmail.com>
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
0
Philip
6/26/2015 5:10:17 PM
mozilla.dev.apps.seamonkey 1527 articles. 1 followers. Post Follow

2 Replies
263 Views

Similar Articles

[PageSpeed] 25

W dniu 06/26/2015 o 07:10 PM, Philip Chee pisze:
> My main problem was getting Chatzilla and DOMI to build. Due to
> incompatible changes in the moz.build process on trunk. Chatzilla and
> DOMI cannot be built off tip.

Interesting thing: I did only run into this scenario with SM 2.35 from
comm-release, when using client.py with the tag/branch-name like "python
client.py default".
When letting client.py decide, everything went well (but it uses then
mozilla-release insteas of mozilla-esr38, of course).

As can be seen here:
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-linux32/
the DOMi and ChatZilla versions are bit older then (2.0.15 and 0.9.91),
so AMO decides immediately to update them, in this case.
0
Adrian
6/26/2015 6:33:15 PM
> I am currently building test 2.35 builds

Hi,

will we have something like an official Beta or even Release Candidate?

CU

Rainer
0
Rainer
7/5/2015 2:18:50 PM
Reply: