STEPS TO REPRODUCE: 1) Start seamonkey trunk nightly (from tarball) on Linux 2) Kill it with -SEGV EXPECTED RESULTS: Get talkback ACTUAL RESULTS: Nothing This worked in a 2005-10-13-06 Linux build, but is broken in a 2005-10-14-06 build and builds thereafter. Talkback is just not shipped -- |find seamonkey -name "*talkback*"| doesn't find any files in the directory that I untarred the tarball into. Per bug bug 312841 comment 21 at least Linux and Windows installer builds are also affected -- the talkback package is just not being built right. I've crashed about a dozen times in the last day with a trunk build, and it'd really be nice to know why. :( So what changed in the tinderbox config between the 13th and 14th to make it not build (or ship?) talkback anymore?
Is this not the same problem as bug 313912 ?
*** This bug has been marked as a duplicate of 313912 ***
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → DUPLICATE
(In reply to comment #0) > Per bug bug 312841 comment 21 at least Linux and Windows installer builds are > also affected -- the talkback package is just not being built right. > > So what changed in the tinderbox config between the 13th and 14th to make it > not build (or ship?) talkback anymore? In my experience, tinderbox builds were build with dummys, only nightlies got the real talkback. And I never found if Talkback was missing in the windows-xpi directory, that it was included in the exe or zip-build. So the builds are always correctly configured as tinderbox builds, having a dummy. They don't switch to including the real thing when building a nightly. So if you want to know if talkback is included in a nightly, have a look into the linux-xpi directory.
Component: Tinderbox Configuration → Tinderbox
Product: mozilla.org → Webtools
You need to log in before you can comment on or make changes to this bug.