after pkgng update, daily run still using pkg_info

Gary Aitken ah at
Sun Sep 29 22:14:17 UTC 2013

>>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?


More information about the freebsd-questions mailing list