From owner-freebsd-questions@FreeBSD.ORG Mon Apr 4 16:10:56 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0244516A4CE for ; Mon, 4 Apr 2005 16:10:56 +0000 (GMT) Received: from ns1.tiadon.com (SMTP.tiadon.com [69.27.132.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A4C943D46 for ; Mon, 4 Apr 2005 16:10:55 +0000 (GMT) (envelope-from kdk@daleco.biz) Received: from [69.27.131.0] ([69.27.131.0]) by ns1.tiadon.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 4 Apr 2005 11:13:25 -0500 Message-ID: <4251670B.8080309@daleco.biz> Date: Mon, 04 Apr 2005 11:10:51 -0500 From: Kevin Kinsey User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Richard Danter References: <42515DCE.2010207@ntlworld.com> In-Reply-To: <42515DCE.2010207@ntlworld.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Apr 2005 16:13:25.0960 (UTC) FILETIME=[3B377C80:01C53931] cc: freebsd-questions@freebsd.org Subject: Re: portupgrade failing on firefox and thunderbird X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2005 16:10:56 -0000 Richard Danter wrote: > Hi all, > > I am trying to update my installations of firefox and thunderbird. I have > done this several times in the past with no problems but lately I get the > following errors (see below). Anyone else seeing this? I can update > other ports just fine... > > Thanks > Rich Well, the output you sent tells us that you have a "checksum mismatch" for the firefox tarball. Basically, the firefox tarball is corrupt - the system can't verify that it's the right file. Most likely, a tarball was partially downloaded, and for some reason was truncated before fetch got finished with it (e.g. connection dropped, you control-C'ed out to do something else, whatever), or it's possible that the file was simply corrupted in transfer. This is a pretty easy fix --- all you should have to do is delete the bad tarball from /usr/ports/distfiles and start the process again. HTH, Kevin Kinsey