Tracking bug for build and release of SeaMonkey 2.49.5
Categories
(SeaMonkey :: Release Engineering, enhancement, P1)
Tracking
(seamonkey2.49esr affected)
| Tracking | Status | |
|---|---|---|
| seamonkey2.49esr | --- | affected |
People
(Reporter: frg, Assigned: ewong)
References
()
Details
Attachments
(13 files, 3 obsolete files)
| Reporter | ||
Updated•6 years ago
|
| Reporter | ||
Updated•6 years ago
|
| Reporter | ||
Comment 1•6 years ago
|
||
| Reporter | ||
Comment 2•6 years ago
|
||
| Reporter | ||
Comment 3•6 years ago
|
||
| Reporter | ||
Comment 4•6 years ago
|
||
| Reporter | ||
Comment 5•6 years ago
|
||
| Reporter | ||
Updated•6 years ago
|
| Assignee | ||
Comment 6•6 years ago
|
||
| Reporter | ||
Comment 7•6 years ago
|
||
| Reporter | ||
Comment 8•6 years ago
|
||
| Reporter | ||
Comment 9•6 years ago
|
||
| Reporter | ||
Comment 10•6 years ago
|
||
| Reporter | ||
Comment 11•6 years ago
|
||
Comment 12•6 years ago
|
||
Comment 13•6 years ago
|
||
Comment 14•6 years ago
|
||
Comment 15•6 years ago
|
||
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 16•6 years ago
|
||
Notes regarding this patch:
- It's based on the new_infra_clean branch and not the seamonkey-production
one that we used to use. The new BB infra uses BB 1.20 which requires
some upheaval (and personal touches). - This patch is to give our new bb something to chew on as it's failing
with c-c. - I expect the build # to rack up. (Place your bets here.... :P )
| Reporter | ||
Comment 17•6 years ago
|
||
Updated the branches and now you have the review honor :)
Changes:
- milestone is 52.9.1.
- new csets for comm-esr52 and mozilla-esr52
- branch SEAMONKEY_2_49_ESR_RELBRANCH from comm-esr52. I suspect relbranchPrefix": "SEA_COMM" needs to be adjusted or a new tag is needed.
l10n tags are unchanged from 2.49.4. I didn't verify the file.
| Assignee | ||
Comment 18•6 years ago
|
||
| Assignee | ||
Comment 19•6 years ago
|
||
| Reporter | ||
Comment 20•6 years ago
|
||
| Assignee | ||
Comment 21•6 years ago
|
||
Comment on attachment 9036249 [details] [diff] [review]
Use vs2017 for building. Pushed see comment 33
need to push this to comm-esr52
Comment 22•6 years ago
|
||
Comment on attachment 9036249 [details] [diff] [review]
Use vs2017 for building. Pushed see comment 33
a=me
| Reporter | ||
Comment 23•6 years ago
|
||
cset from comm-esr52 corrected after latest config push. r+ retained.
| Reporter | ||
Comment 24•6 years ago
|
||
opps wrong file. r+ retained.
| Reporter | ||
Comment 25•6 years ago
|
||
Comment on attachment 9036278 [details] [diff] [review]
2.49.5 build config pushed in comment 28
ewong for the push I can't find the new branch you mentioned in buildbot config. Do I/we need to create one?
| Assignee | ||
Comment 26•6 years ago
|
||
(In reply to Frank-Rainer Grahl (:frg) from comment #25)
Comment on attachment 9036278 [details] [diff] [review]
2.49.5 build configewong for the push I can't find the new branch you mentioned in buildbot
config. Do I/we need to create one?
It should be there.
| Reporter | ||
Comment 27•6 years ago
|
||
Thanks. Didn't know about this one. Only knew the seamonkey-production branch in the normal repo.
https://hg.mozilla.org/build/buildbot-configs/
| Reporter | ||
Comment 28•6 years ago
|
||
Comment on attachment 9036278 [details] [diff] [review]
2.49.5 build config pushed in comment 28
https://hg.mozilla.org/SeaMonkey/buildbot-configs/rev/682f632b4c1d4b9faf011745cf2aebcbcba44ec7
| Reporter | ||
Updated•6 years ago
|
| Reporter | ||
Comment 30•6 years ago
|
||
| Reporter | ||
Updated•6 years ago
|
| Reporter | ||
Comment 31•6 years ago
|
||
| Reporter | ||
Comment 32•6 years ago
|
||
| Reporter | ||
Comment 33•6 years ago
|
||
| Reporter | ||
Updated•6 years ago
|
| Reporter | ||
Comment 34•6 years ago
|
||
Allows to use a branch for checkout. I didn't try a clone but should work too.
Uses the default changesets for cZ and DOMi which are compatible with 2.49.5
If rev is specified this will be used for the update. Incompatible with branch but if the rev is in the branch the source will be updated to it.
| Reporter | ||
Comment 35•6 years ago
|
||
Patch for our SEAMONKEY_2_49_RELBRANCH to undo the changes done to disable extension building because of l10n bug 1231349
r+ a+ some time ago from IanN over irc. If not let me know.
There is no easy way to set a branch to the default branch and we did sone changes in between to the branch so backing out the original changes would be cumbersome.
Comment 36•6 years ago
|
||
| Reporter | ||
Comment 37•6 years ago
|
||
The final fixes have been pushed and we are hopefully done with the source:
https://hg.mozilla.org/releases/comm-esr52/pushloghtml?changeset=6b30146aa4117616f2570fe192eaad1938fa5416
https://hg.mozilla.org/releases/mozilla-esr52/pushloghtml?changeset=3a4afe7ecac570decfb1d388eee2682d5d15dbc8
| Reporter | ||
Updated•6 years ago
|
| Reporter | ||
Updated•6 years ago
|
| Reporter | ||
Updated•6 years ago
|
| Reporter | ||
Comment 38•6 years ago
|
||
| Reporter | ||
Comment 39•6 years ago
|
||
| Reporter | ||
Comment 40•6 years ago
|
||
Comment 41•6 years ago
|
||
Considering Attachment #9073439 [details] [diff] (restore extensions patch):
I try to disable irc and inspector at build time (yes, questionable idea, but it is buid od a package for a distribution with its own rules etc.)
For this, I specify "--enable-extensions=default,-inspector,-irc" (or just "--enable-extensions=gio" to avoid defaults).
It leads to a situation when dist/bin/distribution/extensions directory just does not exist (since nothing need it). And then suite/app/Makefile complains:
make[5]: *** No rule to make target ../../dist/bin/distribution/extensions', needed bypack-ext'. Stop.
Manually adding of this dir removes the message only, the things still are failed anyway.
| Reporter | ||
Comment 42•6 years ago
|
||
This is fixed in bug 1559419. So far I was under the assumption that it does not apply to comm-esr52. If we need another 2.49 I will add it there too but just putting the line in app/Makefile.in should fix it for local builds.
Comment 43•6 years ago
|
||
Yep, still missing in build3
Comment 44•6 years ago
|
||
Well, the patch from bug #1559419 fixes the build itself, but there are still issues when I make langpacks (a bit separately from the usual build process).
After the normal build is complete, I perform:
pushd obj-*/suite/locales
for lang in $languages
do
make merge-$lang LOCALE_MERGEDIR=../../l10n-merges
make langpack-$lang LOCALE_MERGEDIR=../../l10n-merges
donepopd
and for the first lang(=cs) in the list "make langpack-cs" faled with:
make: *** ../../extensions/irc/locales: No such file or directory. Stop.
make: *** [libs-cs] Error 2
Since ready-made xpi langpacks (as in 2.49.4) no more provided, it is an issue.
(BTW, whether it is possible to have version, or date, or git etc. in the name of l10n tarball? And it would be fine to have one common initial subdir in tarball as well...)
Comment 45•6 years ago
|
||
whether it is possible to have version
Sure it has. No more work at the night... :)
Having common initial subdir for l10n tarball would be fine for rpm-based distros.
Comment 46•6 years ago
|
||
One more patch needed to build SM-2.49.5 with system nss/nspr.
Something changed since 2.49.4, and now we should remove "crmf" stuff there.
Probably related somehow to bug #1371991 , but it removes in another place...
| Reporter | ||
Comment 47•6 years ago
|
||
The l10n tarball is available in
https://archive.mozilla.org/pub/seamonkey/candidates/2.49.5-candidates/build3/source/
Comment 48•6 years ago
|
||
make: *** ../../extensions/irc/locales: No such file or directory. Stop.
make: *** [libs-cs] Error 2
can be fixed by a kludge:
diff -Nrbu seamonkey-2.49.5/seamonkey-2.49.5/suite/locales/Makefile.in seamonkey-2.49.5-OK/seamonkey-2.49.5/suite/locales/Makefile.in
--- seamonkey-2.49.5/seamonkey-2.49.5/suite/locales/Makefile.in 2019-07-14 00:01:29.000000000 +0300
+++ seamonkey-2.49.5-OK/seamonkey-2.49.5/suite/locales/Makefile.in 2019-08-19 22:45:21.358643583 +0300
@@ -123,7 +123,7 @@
@$(MAKE) -C $(DEPTH)/toolkit/locales libs-$*
@$(MAKE) -C $(DEPTH)/services/sync/locales AB_CD=$* XPI_NAME=locale-$*
@$(MAKE) -C ../../editor/ui/locales AB_CD=$* XPI_NAME=locale-$*
- @$(MAKE) -C $(DEPTH)/extensions/irc/locales libs-$*
+ @$(MAKE) -C $(DEPTH)/extensions/irc/locales libs-$* || :
@$(MAKE) -C $(DEPTH)/extensions/spellcheck/locales AB_CD=$* XPI_NAME=locale-$*
@$(MAKE) -C $(DEPTH)/intl/locales AB_CD=$* XPI_NAME=locale-$*
@$(MAKE) -C $(DEPTH)/devtools/client/locales AB_CD=$* XPI_NAME=locale-$*
But then, at "make install" stage,
Error: /home/buc/rpmbuild/BUILD/seamonkey-2.49.5/seamonkey-2.49.5/obj-x86_64-pc-linux-gnu/suite/installer/package-manifest:639: Missing file(s): bin/distribution/extensions/{59c81df5-4b7a-477b-912d-4e0fdf64e5f2}.xpi
Error: /home/buc/rpmbuild/BUILD/seamonkey-2.49.5/seamonkey-2.49.5/obj-x86_64-pc-linux-gnu/suite/installer/package-manifest:642: Missing file(s): bin/distribution/extensions/inspector@mozilla.org.xpi
It seems that [chatzilla] and [inspector] sections should be ifdef'ed (like for MOZ_CALENDAR) in suite/installer/package-manifest.in ...
Is it applicable just to remove unneeded distribution/extensions/* files after the package is built, instead of non-working "--enable-extensions"? Or maybe its presence is mentioned something else in the generated code?
| Reporter | ||
Comment 49•6 years ago
|
||
Well we were actually happy to build them again so tests disabling them were not really done. This is all fixed in 2.53 and up where you can turn them on and off in the mozconfig with enable directives.
You can try backing out https://hg.mozilla.org/releases/comm-esr52/rev/3fe8be0e3a645eb17b5e4ac6902677014102706d which will restore the 2.49.4 state for extensions.
Comment 50•6 years ago
|
||
This is all fixed in 2.53 and up where you can turn them on and off in the mozconfig with enable directives.
Fine.
Then bug #1512882 comment #46 still remains for me (ie. build with system nss).
| Reporter | ||
Comment 51•6 years ago
|
||
Then bug #1512882 comment #46 still remains for me (ie. build with system nss).
Some time ago backported and so fixed in 2.53 too. When 2.49.5 is released we hope to do a 2.53 beta soon. We do not plan to fix anything else in 2.49.x.
| Reporter | ||
Comment 52•6 years ago
|
||
The journey of esr52 has come to an end unless a major bug is discovered soon. Thanks to all involved and see you in 2.53.
Description
•