Closed Bug 302745 Opened 19 years ago Closed 19 years ago

talkback.xpi is (almost) empty in 1.7.11 linux release

Categories

(SeaMonkey :: Build Config, defect)

1.7 Branch
x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: hugues.fournier, Assigned: chase)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050722 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.7.11) Gecko/20050728

In the 1.7.11 linux i686 release, talkback.xpi only contains install.js.
This is causing a -214 error (DOES_NOT_EXIST) when addDirectory("Program",
"1.7.11", "bin", communicatorFolder, "", true ) is called in install.js as bin
doesn't exist in the archive, and the user get a -201 error (UNEXPECTED_ERROR)
in the installer.

(For this reason, in the french l10n version of the installer , I chose to
comment out the talkback component in the config.ini file)

I had to comment the installation


Reproducible: Always

Steps to Reproduce:
1. Download the linux installer (or stub-installer)
2. Install it

Actual Results:  
When the talkback component is being installed, the installer returns a -201
error (not fatal for the installation) because of this almost empty

Expected Results:  
The talkback xpi should have installed seamlessly.

Relevant install log lines:
     Quality Feedback Utility (version 1.7.11)
     ------------------------

     ** initInstall: 0
     ** communicatorFolder: /home/hugues/mozilla-test/
     ** addDirectory() returned: -214
     ** cancelInstall() returned: -214

     Install **FAILED** with error -214  --  2005-07-30 07:19:40
(In reply to comment #0)
> Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.7.11) Gecko/20050728

Despite the UA I wrote, this is affecting en-US version too.
(Sorry for the noise)
Version: unspecified → 1.7 Branch
*** Bug 302747 has been marked as a duplicate of this bug. ***
mozilla/nightly/2005-07-28-07-1.7/linux-xpi
talkback.xpi                                        28-Jul-2005 16:57  1.1K 

mozilla/nightly/2005-07-29-11-1.7/linux-xpi
talkback.xpi                                        29-Jul-2005 21:42  781K 

but the parent directory holds nothing but linux-xpi:
http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/2005-07-29-11-1.7/
Assignee: xpi-packages → nobody
Status: UNCONFIRMED → NEW
Component: Installer: XPI Packages → Build Config
Ever confirmed: true
QA Contact: build-config
Flags: blocking1.7.11?
Oops, 1.7.11 already released =(
Flags: blocking1.7.11?
It is not yet announced, didn`t see it a planet.mozilla.org, mozillazine, etc.
Mozilla.org offers download of 1.7.10,
http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/ offers 1.7.8 (don't
know which mirror that is), 

Bug seen in:
http://mozilla.osuosl.org/pub/mozilla.org/mozilla/releases/mozilla1.7.11/linux-xpi/
talkback.xpi                                     29-Jul-2005 18:21  1.1K 

Could this yet be stopped, or the correct talkback.xpi loaded?
Severity: normal → critical
It was announced, inofficially:

Mozilla 1.7.11 has been released
MozillaZine Forum Index -> SeaMonkey Builds 
http://forums.mozillazine.org/viewtopic.php?p=1640858#1640858

There are no relnotes yet, maybe there should be a short note about the missing
talkback on Linux.
Hi,
And It appears to be missing in the Linux tar.gz
http://mozilla.isc.org/pub/mozilla.org/mozilla/releases/mozilla1.7.11/mozilla-i686-pc-linux-gnu-1.7.11.tar.gz
build too.
It seems to be missing in the linux builds all together.
Hi,
I was just looking into this more and it looks like it could be a build machine
configuration problem.
Could someone please check that tinderbox.?
Assignee: nobody → chase
Hi,
I am requesting blocking 1.7.12 becuse of a tinderbox issue
Look at
ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/tinderbox-builds/maple-1.7/linux-xpi
It is also having the 1.1 talkback.xpi file.
Flags: blocking1.7.12?
Or
http://ftp.mozilla.org/pub/mozilla.org/mozilla/tinderbox-builds/maple-1.7/linux-xpi
Please use this link instead.
These are the tinderbox builds.
(In reply to comment #10)

> These are the tinderbox builds.

Usually tinderbox builds are delivered with dummy talkback.xpi, not the real
thing. The exemption is the tinderbox build which will be delivered as nightly.
if the windows-xpi or linux-xpi directory is showing the dummy talkback.xpi, a
few kb instead of a few hundred kb, talkback isnΒ΄t packaged in all versions for
that os, zip, installer, netinstaller.
Hi,
In that case I am removing the blocking request.
Flags: blocking1.7.12?
maple's 7/28 release cycle has this error:

U fullsoft/runtime/unix/Linux2_x86/talkback
U fullsoft/runtime/unix/Linux2_x86/talkback.so
cvs checkout: Updating fullsoft/runtime/unix/SunOS5_sparc
Read from remote host cvs.mozilla.org: Connection timed out
NEXT ERROR cvs [checkout aborted]: end of file from server (consult above
messages if any)

Looks like the connection to the CVS server failed while it was pulling the
Talkback module.
(In reply to comment #3)
> mozilla/nightly/2005-07-28-07-1.7/linux-xpi
> talkback.xpi                                        28-Jul-2005 16:57  1.1K 
> 
> mozilla/nightly/2005-07-29-11-1.7/linux-xpi
> talkback.xpi                                        29-Jul-2005 21:42  781K 
> 
> but the parent directory holds nothing but linux-xpi:
> http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/2005-07-29-11-1.7/

I've forced the upload of the 7/29 release cycle to the nightly directory.
Hi,
Chase could you reupload the 07-28 maple builds (with the correct talkback.xpi
file) so we can install it ourselfs?
Hi,
Chase could you reupload the 07-28 maple builds (with the correct talkback.xpi
file) so we can install it ourselfs?
sorry for dupe I make mistake.
Hi,
And when I used the stub installer I got an error -621. When it was installing
to the Hard drive.
Depends on: 302872
No longer depends on: 302872
Hi,
I have written https://bugzilla.mozilla.org/show_bug.cgi?id=302872 to try to fix
this problem.
Hi,
What we could do is update the linux builds to the 07-29 builds that have the
correct talkback.xpi file.
*** Bug 302872 has been marked as a duplicate of this bug. ***
(In reply to comment #20)
> What we could do is update the linux builds to the 07-29 builds that have the
> correct talkback.xpi file.

Believe me, Chase knows what we can do, and he is working on a solution.

What you could do to help is to test the builds Chase commented about in comment
14 and tell if they are working correctly, i.e. if all variants, including the
installers, work correctly, and if talkback get installed and used in those.
Hi,
Updated builds are now avaible.
See http://mozilla.osuosl.org/pub/mozilla.org/mozilla/releases/mozilla1.7.11/
I think you should announce about linux build's update right now.
Many localizers already working with existing no-talkback builds.
Please never replace released builds without announce to localizers.

Making fixed build is not problem but replacing without announce
will lose localizer's motivation. So, Please.
A short description needed for release page.

See
http://www.mozilla.org/releases/#1.6b
http://www.mozilla.org/releases/#1.6a

"The original Linux builds were..."
"New builds are available as of..."
(In reply to comment #25)
> A short description needed for release page.

But in this case the builds were replaced *before* it was released on the Web site.
(In reply to comment #26)
> But in this case the builds were replaced *before* it was released on the Web
site.

But some users (and many localizers) have already downloaded these builds from
FTP. Only a short description makes everyone happy :-)
http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.7.11/linux-xpi/
 talkback.xpi                                     29-Jul-2005 19:28  781K 
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
For localizers, I (dynamis) posted to L10N NG about this.
http://groups.google.co.jp/group/netscape.public.mozilla.l10n/browse_frm/thread/52c6cd026ab3ddb4/ca90b342343db361?tvc=1
If my message includes something wrong, correct it in the NG please.
Thanks.
*** Bug 320959 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.