From owner-freebsd-questions@FreeBSD.ORG Sun Aug 23 08:56:23 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37C18106568B for ; Sun, 23 Aug 2009 08:56:23 +0000 (UTC) (envelope-from mail@ozzmosis.com) Received: from smtp.mel.people.net.au (smtp.mel.people.net.au [218.214.17.98]) by mx1.freebsd.org (Postfix) with SMTP id 713298FC1F for ; Sun, 23 Aug 2009 08:56:22 +0000 (UTC) Received: (qmail 30267 invoked from network); 23 Aug 2009 08:56:07 -0000 Received: from unknown (HELO smtp.phoenix) (218.215.173.67) by smtp.mel.people.net.au with SMTP; 23 Aug 2009 08:56:07 -0000 Received: by smtp.phoenix (Postfix, from userid 1001) id 2627B171C1; Sun, 23 Aug 2009 18:56:19 +1000 (EST) Date: Sun, 23 Aug 2009 18:56:19 +1000 From: andrew clarke To: freebsd-questions Message-ID: <20090823085619.GA78363@ozzmosis.com> References: <20090823082453.GA75105@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090823082453.GA75105@xs4all.nl> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Vincent Zee Subject: Re: MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Aug 2009 08:56:23 -0000 On Sun 2009-08-23 10:24:53 UTC+0200, Vincent Zee (zenzee@xs4all.nl) wrote: > ===> Vulnerability check disabled, database not found > ===> Extracting for netatalk-2.0.4,1 > => MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2. > => SHA256 Checksum mismatch for netatalk-2.0.4.tar.bz2. I'm getting a checksum mismatch here too. This probably means the tarball was modified. > I checked the distinfo file and it is the same as on my other machine. > On which the update went fine. Solution #1: Use "make NO_CHECKSUM=yes", just ignore the mismatch and hope it will build. Solution #2: Copy /usr/ports/distfiles/netatalk-2.0.4.tar.bz2 from your other machine and rebuild. Solution #3: Don't bother building from ports if you already have a working binary on your other machine. Use "pkg_create -vb netatalk\*", copy the resulting file to the new machine, then use pkg_add. This assumes the same architecture (eg. i386) on both machines.