From owner-freebsd-questions@FreeBSD.ORG Fri May 16 09:19:51 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 5441037B401 for ; Fri, 16 May 2003 09:19:51 -0700 (PDT) Received: from morpheus.mind.net (morpheus.mind.net [69.9.130.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9033243F3F for ; Fri, 16 May 2003 09:19:50 -0700 (PDT) (envelope-from jfox@morpheus.mind.net) Received: from morpheus.mind.net (localhost [127.0.0.1]) by morpheus.mind.net (8.12.6/8.12.6) with ESMTP id h4GGJnCj021271 for ; Fri, 16 May 2003 09:19:50 -0700 (PDT) (envelope-from jfox@morpheus.mind.net) Received: (from jfox@localhost) by morpheus.mind.net (8.12.6/8.12.6/Submit) id h4GGJnFC021270 for freebsd-questions@freebsd.org; Fri, 16 May 2003 09:19:49 -0700 (PDT) Date: Fri, 16 May 2003 09:19:49 -0700 From: John Fox To: freebsd-questions@freebsd.org Message-ID: <20030516161948.GB94908@mind.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: missing +CONTENTS file 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: Fri, 16 May 2003 16:19:51 -0000 This is very interesting. I ran 'pkg_info' on one of my machines here, and amongst the output was "pkg_info: unable to open +CONTENTS file". I poked around a bit, and determined that the pine-4.44 package was the only one lacking a +CONTENTS file in its /var/db/pkg directory, and am curious about a couple of things: 1) I am relatively certain that nobody deliberately erased that file, and the rest of the directory seems intact. This brings to mind the possiblity of a bug, and I have gone through the listing of open bug reports, searching for the described behavior, and found nothing. (There were many instances of 'pkg', but I am reasonably certain I didn't miss any.) So I ask now if any of you have observed this sort of behavior. 2) I am guessing I can fix this by deleting the package and reinstalling it, but would appreciate some feedback from others before doing so, as this issue is on a production machine, and I'd hate to further mess up the pkg/db structure. With thanks, John -- +---------------------------------------------------------------------------+ | John Fox | System Administrator | InfoStructure | +---------------------------------------------------------------------------+ | "The people and friends that we have lost, the dreams that have faded... | | never forget them." -- Yuna, Final Fantasy X | +---------------------------------------------------------------------------+