L10N verification for repacks of 4.0b7+ has the following warning: warning [./firefox/omni.jar]: 3352229 extra bytes at beginning or within zipfile (attempting to process anyway) error [./firefox/omni.jar]: reported length of central directory is -3352229 bytes too long (Atari STZip zipfile? J.H.Holm ZIPSPLIT 1.1 zipfile?). Compensating... I manually checked the files on macosx64 (where we do l10n verification) and linux platforms and tried to unzip omni.jar (UnZip 5.52 of 28 February 2005, by Info-ZIP on both platforms). I had the same warning *only* for non en-US packages (l10n repacks). No such warning for en-US builds. To make sure that this is not a stopper for b8 I unpacked omni.jar with 7z and compared the directories. Fortunately they were without any difference. I suspect that the new omni.jar uses new features of zip (zip64?). In this case we should switch to a newest version of unzip or 7z. Additionally we should investigate why we have these warning for l10n repacks only.

This is the result of bug 559961. It's mostly harmless though it confuses many zip programs.

rail, do you recall how you managed to convince 7z to unpack omni.jar ? I get 7-Zip 9.13 beta Copyright (c) 1999-2010 Igor Pavlov 2010-04-15 p7zip Version 9.13 (locale=utf8,Utf16=on,HugeFiles=on,2 CPUs) Processing archive: ../omni.jar Error: Can not open file as archive There's nothing obvious in the changelog for 7zip (http://www.7-zip.org/history.txt) between 9.13 and 9.20.

7zip can't open these zip files see: http://sourceforge.net/tracker/?func=detail&atid=114481&aid=3065694&group_id=14481 and https://bugzilla.mozilla.org/show_bug.cgi?id=605524

(In reply to comment #2) > rail, do you recall how you managed to convince 7z to unpack omni.jar ? I get It was unzip: http://hg.mozilla.org/build/tools/rev/483d22dfacf8

Still an issue?

(In reply to Aki Sasaki [:aki] from comment #5) > Still an issue? rail: ping - is this still a problem or can we close this bug?

(In reply to John O'Duinn [:joduinn] from comment #6) > (In reply to Aki Sasaki [:aki] from comment #5) > > Still an issue? > > rail: ping - is this still a problem or can we close this bug? Yes, those warnings still happen.

We are going to remove l10n verify builders in the nearest future.