From owner-freebsd-ports-bugs@FreeBSD.ORG Wed Sep 20 16:53:11 2006 Return-Path: X-Original-To: freebsd-ports-bugs@FreeBSD.org Delivered-To: freebsd-ports-bugs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D18C16A47E for ; Wed, 20 Sep 2006 16:53:11 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp1.utdallas.edu (smtp1.utdallas.edu [129.110.10.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70DE643D8B for ; Wed, 20 Sep 2006 16:53:07 +0000 (GMT) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) by smtp1.utdallas.edu (Postfix) with ESMTP id 69DCB388F60 for ; Wed, 20 Sep 2006 11:52:24 -0500 (CDT) Date: Wed, 20 Sep 2006 11:48:47 -0500 From: Paul Schmehl To: freebsd-ports-bugs@FreeBSD.org Message-ID: In-Reply-To: <20060920054146.GJ61429@graf.pompo.net> References: <20060919191641.GB52391@graf.pompo.net> <20060920054146.GJ61429@graf.pompo.net> X-Mailer: Mulberry/4.0.5 (Linux/x86) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========04ABC67E2F149596C083==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Checksum mismatch for print/fpdf X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2006 16:53:11 -0000 --==========04ABC67E2F149596C083========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Wednesday, September 20, 2006 07:41:46 +0200 Thierry Thomas=20 wrote: >> >> Even after deleting the port and cvsuping it again, it fails the >> checksum. Maybe it's because it's an AMD box? > > Rather strange! Is your file a valid .tgz? > Could you please untar it and diff it (`diff -urN') against > > ? > I ran the diff. They were definitely different files. Binary files test/fpdf153(2).tgz and test1/fpdf153(2).tgz differ Binary files test/fpdf153.tgz and test1/fpdf153.tgz differ So I ran make distclean, then attempted to portupgrade the port, and it=20 worked fine. Apparently, when portupgrade d/l'd the file it was corrupted=20 somehow. Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========04ABC67E2F149596C083==========--