From owner-freebsd-questions@FreeBSD.ORG Wed Sep 17 19:17:02 2003 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 29AD216A4B3 for ; Wed, 17 Sep 2003 19:17:02 -0700 (PDT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 575BF43F3F for ; Wed, 17 Sep 2003 19:17:01 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: from be-well.ilk.org (be-well.no-ip.com[66.30.200.37]) by comcast.net (rwcrmhc12) with ESMTP id <20030918021700014001lnvpe>; Thu, 18 Sep 2003 02:17:00 +0000 Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37] (may be forged)) by be-well.ilk.org (8.12.9/8.12.9) with ESMTP id h8I2GxCo062624 for ; Wed, 17 Sep 2003 22:16:59 -0400 (EDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.9/8.12.6/Submit) id h8I2GxDe062615; Wed, 17 Sep 2003 22:16:59 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-questions-local@be-well.ilk.org using -f Sender: lowell@be-well.no-ip.com To: freebsd-questions@freebsd.org References: From: Lowell Gilbert Date: 17 Sep 2003 22:16:58 -0400 In-Reply-To: Message-ID: <44llsm7sdh.fsf@be-well.ilk.org> Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: ghostscript-gnu distfile checksum error - WORKAROUND (was: Stop error installing /usr/ports/mail/evolution) 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: Thu, 18 Sep 2003 02:17:02 -0000 Barry Hawkins writes: > My own research via Google showed several places I could try > to download the problematic Samsung-SmartGDI-all-GS.tar.gz. After > downloading the file in question several times from different > locations, including the FreeBSD ftp archives, I continued to receive > the same messages regarding checksum failures. > I came across one person's workaround, and was able to use > that 002738.html>. However, there are several old postings in various > newsgroups about this problem, some dating back to October 2002. Why > hasn't this MD5 checksum issue been corrected yet? Is there another > dependent issue that justifies not fixing this? If I fetch it right now, it fetches fine and matches the checksum. There's nothing wrong with the port -- the problem is in your system failing to get the file. Remove it, and let the ports system get it on its own, and I *suspect* that the ports system will get it right.