From owner-freebsd-questions@FreeBSD.ORG Sat May 11 20:30:24 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9A27FE37; Sat, 11 May 2013 20:30:24 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 7A9BC7E0; Sat, 11 May 2013 20:30:23 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 2C5F53AF45; Sat, 11 May 2013 13:30:18 -0700 (PDT) From: "Ronald F. Guilmette" To: CyberLeo Kitsana Subject: Re: WANTED: Tool to verify installed package/port consistancy In-Reply-To: <518E1A51.3020702@cyberleo.net> Date: Sat, 11 May 2013 13:30:18 -0700 Message-ID: <96251.1368304218@server1.tristatelogic.com> Cc: John Levine , freebsd-questions@freebsd.org, freebsd-ports@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 May 2013 20:30:24 -0000 In message <518E1A51.3020702@cyberleo.net>, you wrote: >On 05/10/2013 03:04 PM, Ronald F. Guilmette wrote: > >> pkg_sanity: ImageMagick-6.8.0.7_1: +CONTENTS file does not exist -- skipped >> pkg_sanity: ORBit2-2.14.19: /usr/local/lib/libORBit-2.so: File failed MD5 checksum >> pkg_sanity: ORBit2-2.14.19: /usr/local/lib/libORBit-imodule-2.so: File failed MD5 checksum >> pkg_sanity: ORBit2-2.14.19: /usr/local/lib/libORBitCosNaming-2.so: File failed MD5 checksum >> pkg_sanity: OpenEXR-1.7.1: /usr/local/lib/libIlmImf.so: File failed MD5 checksum >> pkg_sanity: aalib-1.4.r5_6: /usr/local/lib/libaa.so: File failed MD5 checksum > > >Are these mismatches symlinks? Some are. >If so, are you checking the contents of >the symlink (with, for instance, stat(1) or readlink(1)), or the >contents of the file to which the symlink is referring? The latter. (I would have had to have done something special in order to compute the md5 fo teh symlink itself, and I did not do so. I have just now checked, and my script is indeed getting the md5 of the files to which the various symlinks refer.) It is clear to me now that "pkg_info -g" is either skipping certain files that are listed in the relevant +CONTENTS files or else it is computing the MD5 checksums in an odd way. I do not think that the latter possibility is at all likely. I will be looking at this more deeply as time permits. Regards, rfg