pkdgb and corrupted record(s)

Kurt Buff kurt.buff at
Fri Aug 12 22:22:39 UTC 2011

On Fri, Aug 12, 2011 at 12:44, Adam Vande More <amvandemore at> wrote:
> On Fri, Aug 12, 2011 at 1:15 PM, Warren Block <wblock at> wrote:
>> I'd never seen it with portupgrade, either.  Don't know the cause, but it
>> can be a problem.  portmaster --check-depends might fix it.  A more
>> brute-force way is to figure out which are the problems with
>> find /var/db/pkg -name "+CONTENTS" -exec egrep -B1 -H 'pkgdep $' {} \;
>> Then rebuild all of them by feeding the list to portmaster, which will
>> sort them and rebuild in the right order to fix it.
> If I remember correctly, this can be caused by Ctrl-C out of a portmaster
> run early, or perhaps some other abnormal termination.  IIRC, some
> improvements have been done for this problem as it's been quite awhile since
> I've seen it personally, but your mileage may vary.
> --
> Adam Vande More

That sounds reasonable. Don't know that I've ever done that, but
memory dims as I grow older....


More information about the freebsd-questions mailing list