Date: Fri, 12 Aug 2011 12:15:33 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Kurt Buff <kurt.buff@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: pkdgb and corrupted record(s) Message-ID: <alpine.BSF.2.00.1108121211120.55848@wonkity.com> In-Reply-To: <CADy1Ce49fhhVk=tAJ0zeGGHNm=qbhct23AusBKhF3WVwJDWNMA@mail.gmail.com> References: <CADy1Ce49fhhVk=tAJ0zeGGHNm=qbhct23AusBKhF3WVwJDWNMA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 12 Aug 2011, Kurt Buff wrote:
> This seems fairly benign so far, but I find it happening on several
> machines after switching from portupgrade to portmaster. Don't know if
> that switch is actually part of the issue or not, though I'm really
> liking portmaster.
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1108121211120.55848>