This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug web/52200] Archives of some old versions of gcc are corrupted
- From: "maisqual.project at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 10 Feb 2012 21:18:59 +0000
- Subject: [Bug web/52200] Archives of some old versions of gcc are corrupted
- Auto-submitted: auto-generated
- References: <bug-52200-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52200
--- Comment #1 from Boris Baldassari <maisqual.project at gmail dot com> 2012-02-10 21:18:59 UTC ---
Well.. Actually I was NOT able to get them right with bzip2recover.
The gcc-4.6.2.tar.bz2 is corrupted as well. (other not-mentioned releases were
ok).
More information:
* Download the build :
-8<--------------------------------------------------------
boris@server:gcc$ wget http://ftp.gnu.org/gnu/gcc/gcc-4.6.2/gcc-4.6.2.tar.bz2
--2012-02-10 21:29:10-- http://ftp.gnu.org/gnu/gcc/gcc-4.6.2/gcc-4.6.2.tar.bz2
Resolving ftp.gnu.org... 140.186.70.20
Connecting to ftp.gnu.org|140.186.70.20|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 71995338 (69M) [application/x-bzip2]
Saving to: `gcc-4.6.2.tar.bz2'
100%[===========================================================================================================================================================>]
71,995,338 132K/s in 7m 0s
2012-02-10 21:36:11 (167 KB/s) - `gcc-4.6.2.tar.bz2' saved [71995338/71995338]
-8<--------------------------------------------------------
* Untar the file:
-8<--------------------------------------------------------
boris@server:gcc$ wget
http://ftp.gnu.org/gnu/gcc/gcc-4.6.2/gcc-4.6.2.tar.bz2.sig
boris@server:gcc$ tar xjf ../../applis/src/gcc/gcc-4.6.1.tar.bz2
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
-8<--------------------------------------------------------
I verified the signature of the build..
-8<--------------------------------------------------------
boris@server:gcc$ gpg --verify gcc-4.6.2.tar.bz2.sig
gpg: Signature made Wed 26 Oct 2011 14:56:46 CEST using DSA key ID C3C45C06
gpg: Good signature from "Jakub Jelinek <jakub@redhat.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 33C2 35A3 4C46 AA3F FB29 3709 A328 C3A2 C3C4 5C06
-8<--------------------------------------------------------
Could it come from my setup?
Thanks,