Date: Fri, 12 Aug 2011 15:22:37 -0700 From: Kurt Buff <kurt.buff@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: pkdgb and corrupted record(s) Message-ID: <CADy1Ce7XwMHqyCxFmvaG4P=0oG6VD3mpYTTLv6ayEFTzBk=G-Q@mail.gmail.com> In-Reply-To: <CA%2BtpaK32RCOVmMH0_WALO6cyO7UERKYMZME8eq6Zg_sY8jz_3g@mail.gmail.com> References: <CADy1Ce49fhhVk=tAJ0zeGGHNm=qbhct23AusBKhF3WVwJDWNMA@mail.gmail.com> <alpine.BSF.2.00.1108121211120.55848@wonkity.com> <CA%2BtpaK32RCOVmMH0_WALO6cyO7UERKYMZME8eq6Zg_sY8jz_3g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 12, 2011 at 12:44, Adam Vande More <amvandemore@gmail.com> wrote:
> 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
That sounds reasonable. Don't know that I've ever done that, but
memory dims as I grow older....
Kurt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADy1Ce7XwMHqyCxFmvaG4P=0oG6VD3mpYTTLv6ayEFTzBk=G-Q>