From owner-freebsd-questions@FreeBSD.ORG Sun Sep 29 22:14:17 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 834A26A8; Sun, 29 Sep 2013 22:14:17 +0000 (UTC) (envelope-from ah@dreamchaser.org) Received: from nightmare.dreamchaser.org (nightmare.dreamchaser.org [12.32.44.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 49B832BEC; Sun, 29 Sep 2013 22:14:16 +0000 (UTC) Received: from breakaway.dreamchaser.org (breakaway.dreamchaser.org. [12.32.36.73]) by nightmare.dreamchaser.org (8.13.6/8.13.6) with ESMTP id r8TME8EQ000972; Sun, 29 Sep 2013 16:14:09 -0600 (MDT) (envelope-from ah@dreamchaser.org) Message-ID: <5248A630.3030304@dreamchaser.org> Date: Sun, 29 Sep 2013 16:14:08 -0600 From: Gary Aitken User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130730 Thunderbird/17.0.7 MIME-Version: 1.0 To: Mark Felder Subject: Re: after pkgng update, daily run still using pkg_info References: <52470959.9050904@dreamchaser.org> <1380398226.30638.27610565.609ED96A@webmail.messagingengine.com> In-Reply-To: <1380398226.30638.27610565.609ED96A@webmail.messagingengine.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (nightmare.dreamchaser.org [12.32.36.65]); Sun, 29 Sep 2013 16:14:09 -0600 (MDT) Cc: freebsd-questions@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: Sun, 29 Sep 2013 22:14:17 -0000 >>On 09/28/13 10:52, Gary Aitken wrote: >> After switching to pkgng, I noticed that my daily run output constantly >> complains about the installed packages being corrupt, e.g.: >> "pkg_info: the package info for package 'asciidoc-8.6.8_1' is corrupt" >> >> The problem is with >> etc/periodic/daily/490.status-pkg-changes >> which is still using "pkg_info" instead of "pkg info" >> >> Was this script supposed to be automatically updated as part of the >> conversion? What's the "right" way to upgrade this on a 9.1 release >> system? Or should I just edit the script by hand and be done with it? > >On 09/28/13 13:57, Mark Felder wrote: > Run pkg_info. If there is anything listed you have not fully converted > to pkgng and have some old broken/corrupt packages. You'll want to clean > this up. What does "clean this up" mean, and how does one go about it, given the system is converted to using pkgng? There is no /var/db/pkg/pkgdb.db Some of the packages reported as corrupt were installed *after* the conversion to pkgng, so why is pkg_info even noticing them? "pkg info" reports 705 packages installed, and installs and re-installs using portmaster seem to be working. "pkg_info" reports 14 "good" packages and 658 "corrupt" packages. If pkg_info is picking up packages installed after the conversion, why doesn't the sum of good and corrupt packages equal the number pkg reports? It was my understanding that after switching to pkgng, the pkg_* cmds should no longer be used. If that's the case, shouldn't the daily script have been modified by the upgrade process? Gary