Date: Fri, 12 Aug 2011 12:15:29 -0700 From: Kurt Buff <kurt.buff@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: pkdgb and corrupted record(s) Message-ID: <CADy1Ce6iHJGBeWHjnj1vLpiakpMRFGET1zmeinfoTCFEpoZLnQ@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1108121211120.55848@wonkity.com> References: <CADy1Ce49fhhVk=tAJ0zeGGHNm=qbhct23AusBKhF3WVwJDWNMA@mail.gmail.com> <alpine.BSF.2.00.1108121211120.55848@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 12, 2011 at 11:15, Warren Block <wblock@wonkity.com> wrote:
> 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. =C2=A0Don't know the cause, b=
ut it
> can be a problem. =C2=A0portmaster --check-depends might fix it. =C2=A0A =
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 so=
rt
> them and rebuild in the right order to fix it.
I did a 'make deinstall clean' and 'make install' on those packages,
and all is happy now.
Thanks.
Kurt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADy1Ce6iHJGBeWHjnj1vLpiakpMRFGET1zmeinfoTCFEpoZLnQ>