Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <04b701c37ec5$ba80dbd0$12760251@ximenes> From: "Cliff Hones" To: References: <3F6C6A96@webmaila.hku.hk> <047101c37ec0$acaa04f0$12760251@ximenes> Subject: Re: tetex-base 2.0.2-13... Date: Fri, 19 Sep 2003 16:50:18 +0100 Organization: Aonix Europe MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Weiqi Gao wrote: > ... > I had the same problem. Doing a tar jtvf on the bzip2ed tar file > revealed that the download had an integrity problem: > > ============================================================ > -rw-r--r-- root/root 18948 1997-12-26 17:00:00 > usr/share/texmf/fonts/type1/public/cmcyr/cmcbx12.pfb > > bzip2: Data integrity error when decompressing. > Input file = (stdin), output file = (stdout) > ... You are right - it was an earlier version which I thought had got stuck during install. I have just checked the latest package file (from mirrors.rcn.net) and it does have a problem: $ bzcat tetex-base-2.0.2-13.tar.bz2 > /dev/null bzcat: Data integrity error when decompressing. Input file = tetex-base-2.0.2-13.tar.bz2, output file = (stdout) Perhaps the integrity of the package files should be routinely checked when they are added to the master distribution (at the same time the MD5 signatures are calculated). -- Cliff -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/