From mint-bounce@lists.fishpool.fi Fri Aug 20 13:05:42 2010 X-Squirrel-UserHash: EhVcX1lFRQVaRwYcDQ== X-Squirrel-FromHash: UANfXltGQQA= Message-ID: Date: Fri, 20 Aug 2010 19:02:46 +0200 Subject: [MiNT] Trunk daily build is corrupt From: "m0n0" To: mint@lists.fishpool.fi Reply-To: ole@monochrom.net User-Agent: Host Europe Webmailer/1.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-HE-Access: Yes X-bounce-key: webpack.hosteurope.de;ole@monochrom.net;1282323766;3737719d; X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: ole@monochrom.net Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: tar: Record size = 8 blocks 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: Error is not recoverable: exiting now -- Greets, Ole