Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Aug 2011 14:44:26 -0500
From:      Adam Vande More <amvandemore@gmail.com>
To:        Warren Block <wblock@wonkity.com>
Cc:        Kurt Buff <kurt.buff@gmail.com>, freebsd-questions@freebsd.org
Subject:   Re: pkdgb and corrupted record(s)
Message-ID:  <CA+tpaK32RCOVmMH0_WALO6cyO7UERKYMZME8eq6Zg_sY8jz_3g@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 1:15 PM, Warren Block <wblock@wonkity.com> 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



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?CA+tpaK32RCOVmMH0_WALO6cyO7UERKYMZME8eq6Zg_sY8jz_3g>