Hello Managers,
there were no responses on that so far, but I finally found a solution by
myself:
- After some od-ing firefox-2.0.0.12_kit.tar.gz (and reading the gzip
sources) it seemed to me that the gzip error message is triggered by
CR-LF sequences, which might have previously been plain UNIX line
endings (LF only).
- In addition, the gzip FAQ on
http://www.gzip.org states:
99.9% of the problems with gzip are due to file transfers done in
ASCII mode instead of BINARY mode ...
If you have transferred a file in ASCII mode and you no longer have
access to the original, you can try the program fixgz to remove the
extra CR (carriage return) bytes inserted by the transfer. ...
I download and compiled fixgz.c (
http://www.gzip.org/fixgz.c) and after
fixing the firefox-2.0.0.12_kit.tar.gz file provided by HP I was able to
successfully unpack the firefox 2.0.0.12 kit.
$ fixgz firefox-2.0.0.12_kit.tar.gz firefox-2.0.0.12_kit.tar.gz-fixed
$ md5sum firefox-2.0.0.12_kit.tar.gz*
88617a603e9d5241429a86e0ede0763f firefox-2.0.0.12_kit.tar.gz
d74416de378bf697d23455d733b86b0a firefox-2.0.0.12_kit.tar.gz-fixed
$ gtar -tvzf firefox-2.0.0.12_kit.tar.gz-fixed
-rw-r--r-- root/system 428 2008-07-14 15:07:51 Readme.txt
-rw-r--r-- root/system 37442741 2008-07-14 13:56:41 firefox-2.0.0.12-source.tar.bz2
-rw-r--r-- root/system 32194560 2008-07-14 15:04:40 firefox_kit.tar
As the md5sum of the original download matches that indicated on HP's
download page, some person at HP must have done an ASCII ftp transfer ;-)
Franz Fischer's Mail:
> Hello Managers,
>
> I just tried to download the firefox-2.0.0.12_kit.tar.gz file
> from HP and get the file with the same MD5 Checksum as
> given on the download page (88617a603e9d5241429a86e0ede0763f),
> but gzip -dc tells me
>
> gzip: firefox-2.0.0.12_kit.tar.gz: invalid compressed data--format violated
>
> Has anyone else had the same effect?
Regards
\franz
--
Franz G. Fischer ---- tru64 at franz minus fischer dot de
Received on Fri Aug 15 2008 - 18:52:48 NZST